Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Wrong Swap Information on Windows11 #1433

Closed
1 task done
Yikai-Liao opened this issue Mar 26, 2024 · 1 comment · Fixed by #1436
Closed
1 task done

Wrong Swap Information on Windows11 #1433

Yikai-Liao opened this issue Mar 26, 2024 · 1 comment · Fixed by #1436
Labels
bug Something isn't working the way that is expected. duplicate This issue or pull request already exists.

Comments

@Yikai-Liao
Copy link

Checklist

What operating system and version are you using?

Windows 11

What architecture are you using?

x86_64/AMD64

What terminal(s) are you running bottom on that are experiencing the problem?

windows terminal with PowerShell 7.4.1

What filesystem(s) are you using?

NTFS

What version of bottom are you running?

0.9.6

How did you install bottom?

cargo install bottom

Describe the issue

bottom don't show the correct swap memory information on my windows11 laptop.

image

The used SWP memory shown in bottom is the equal to the committed memory shown in the windows task manager, where the committed memory should be the sum of used RAM and SWP.

What is the expected behaviour?

I expect the used SWP shown in btm equal to the cached memory shown in windows task manager.

What is the actual behaviour?

bottom actually shows the committed memory in SWP on Windows 11

How can we reproduce this?

just run bottom on Windows11 and check the windows task manager at the same time.I

Additional information

No response

@Yikai-Liao Yikai-Liao added the bug Something isn't working the way that is expected. label Mar 26, 2024
@ClementTsang
Copy link
Owner

Ah yeah, I think this is known behaviour that I wanted to clarify/fix - see #1052

@ClementTsang ClementTsang added the duplicate This issue or pull request already exists. label Mar 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working the way that is expected. duplicate This issue or pull request already exists.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants