-
-
Notifications
You must be signed in to change notification settings - Fork 285
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
Memory Leak? #96
Comments
Hi, thanks for your message! So far indeed nethogs has not really been optimized for the long-running use case. Presumably there is some leak that makes some data structure grow unbounded, leading to CPU usage when traversing that data structure. I'd welcome help in pinpointing what structure is causing this! |
I left it version 0.8.5-2 running for a week on debian and memory usage was at 4gb |
I also have this bug, using 0.8.5-2, after a few days the memory usage was >1GB, and CPU usage was very high too. |
… as default. - Reduce default frequency to avoid performance issue. - The frequency of it can be modified with `-g` option and can be disabled with `-g 0`.
…proc Issue: #96 - Garbage collect inodeproc on each ui refresh.
Likely fixed by #203 , feel free to open a new issue when you encounter a leak after this change |
I use nethogs 0.8.5 on Linux 4.6.4-1-ARCH and have noticed that when selecting the cumulative MB display by cycling with "m," hours later I can return to the computer to find nethogs crippling my system with its memory usage... or was it CPU? I will confirm.
Has anyone else experienced this?
Edit: It is CPU.
The text was updated successfully, but these errors were encountered: