Open p7r0x7 opened 7 months ago
Probably related to #526.
I have the same bug in the same version (v1.3.2)
It doesn't happen before triggering the tree view and it seems to only affect launchd
EDIT: this bug doesn't occur when Proc aggregate
option is set to False
Reproduced also on MacM1 vtop v1.3.2 current OS. Even with Proc aggregate
set to false but looking at the process tree iterm2 folded.
Describe the bug
7 minutes later...
To Reproduce
On macOS (via the homebrew keg), if you set the proc section to tree and collapse launchd, the memory usage reported by btop escalates dramatically into perpetuity. My 8GB machine is doing just fine reporting 70T of active memory usage (which it also reports as only 900% percent utilization).
Closing and restarting btop yields an identical outcome, with the fictitious number not persisting between program instances.
btop++ v1.3.2