You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In ytop, users trying to run the program with WSL were encountering issues where calling pstuil::memory::virtual_memory() will fail with MissingData due to /proc/meminfo missing MemAvailable. From my brief reading on the topic, this was an attribute that was added in kernel 3.4 (hence my confusion on version 4.4) to give an accurate idea on the amount of available memory left on the system. You can read more on the discussion here where it also mentions that you:
can be estimated from MemFree, Active(file), Inactive(file), and SReclaimable, as well as the "low" watermarks from /proc/zoneinfo.
From this it might be reasonable to provide a fallback where the value is estimated if MemAvailable isn't found in /proc/meminfo.
The text was updated successfully, but these errors were encountered:
Please provide any of the following information if relevant:
3.1.0
(issue is still present in master)uname -a
says 4.4, but behavior seems to deviate from mainline kernelFrom cjbassi/ytop#106
In
ytop
, users trying to run the program with WSL were encountering issues where callingpstuil::memory::virtual_memory()
will fail withMissingData
due to/proc/meminfo
missingMemAvailable
. From my brief reading on the topic, this was an attribute that was added in kernel 3.4 (hence my confusion on version 4.4) to give an accurate idea on the amount of available memory left on the system. You can read more on the discussion here where it also mentions that you:From this it might be reasonable to provide a fallback where the value is estimated if
MemAvailable
isn't found in/proc/meminfo
.The text was updated successfully, but these errors were encountered: