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

[BUG] why do fastfetch and neofetch show different memory ammount being used #1021

Closed
EducatedSuddenBucket opened this issue Jun 18, 2024 · 10 comments
Labels
bug Something isn't working

Comments

@EducatedSuddenBucket
Copy link

screenshot

@EducatedSuddenBucket EducatedSuddenBucket added the bug Something isn't working label Jun 18, 2024
@CarterLi
Copy link
Member

I can't reproduce it. Both fastfetch and neofetch use MemAvailable if available.

https://github.com/dylanaraps/neofetch/blob/master/neofetch#L2691

https://github.com/fastfetch-cli/fastfetch/blob/dev/src/detection/memory/memory_linux.c#L30

What version of fastfetch did you use?

@EducatedSuddenBucket
Copy link
Author

latest , i builded it on debian 12 i386 , it also happened when i used alpine inux

@EducatedSuddenBucket
Copy link
Author

i could also show screen recording if you want

@EducatedSuddenBucket
Copy link
Author

screen-.2.mp4

@CarterLi
Copy link
Member

Seems fastfetch was correct?

@EducatedSuddenBucket
Copy link
Author

see htop at the left

@CarterLi
Copy link
Member

fastfetch prints the same result as free -h

@EducatedSuddenBucket
Copy link
Author

so they are not the same i think

@CarterLi
Copy link
Member

Just found that the change introduced MemAvailable (Nov 3, 2020) in neofetch was committed after the latest release was cut (Aug 3, 2020)

That's it.

@CarterLi CarterLi closed this as not planned Won't fix, can't repro, duplicate, stale Jun 19, 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
Projects
None yet
Development

No branches or pull requests

3 participants