-
Notifications
You must be signed in to change notification settings - Fork 448
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
[BUG] Wrong Used Memory Detection on WSL2 #1096
Comments
neofetch is wrong. Fastfetch uses Neofetch also uses this property. However the change introduced MemAvailable (Nov 3, 2020) in neofetch was committed after the latest release was cut (Aug 3, 2020). You can try the latest neofetch source and it will print similar values as fastfetch. You can also try |
|
It seems that they get different definitions about |
Yeah. |
I'm using debian12 on wls2, ans
fastfetch
tends to show a higher used memory thanneofetch
.I have further checked the used memory shown in
gotop
,htop
andbtm
, and they tend to agree withneofetch
.I haven't check if it could be reproduced on a physical machine.
The text was updated successfully, but these errors were encountered: