gosigar: Overflows in total actual memory/swap
Some issues have been reported regarding weird huge values for used memory or swap. The reported values are near max uint64, and are calculated as Used = Total - Free. It seems that somehow at some moments the reported Free actual memory or swap is greater than Total memory or swap.
Cases reported so far:
About this issue
- Original URL
- State: open
- Created 6 years ago
- Comments: 16 (4 by maintainers)
Hi @michbsd,
Thaks for the info provided, I think that it is being problematic to use the same logic to collect memory stats from Linux and FreeBSD as we do now, so to solve it in FreeBSD we should probably implement its own logic. We have also seen related issues on Linux but maybe they have a different cause. I’d like to take a look to this soon.