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.

Sign up for GitHub

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

Jump to bottom

Memory Leak? #96

Closed
NoSuck opened this issue Sep 9, 2016 · 4 comments
Closed

Memory Leak? #96

NoSuck opened this issue Sep 9, 2016 · 4 comments
Labels
help wanted long-running-usecase

Comments

@NoSuck
Copy link

NoSuck commented Sep 9, 2016 •
edited
Loading

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.
@raboof
Copy link
Owner

raboof commented Dec 30, 2016

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!

@webzorg
Copy link

webzorg commented Sep 19, 2018

I left it version 0.8.5-2 running for a week on debian and memory usage was at 4gb

@wodencafe
Copy link

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.

takeoverjp added a commit to takeoverjp/nethogs that referenced this issue Feb 16, 2021
@takeoverjp
Issue: raboof#96 - Garbage collect inodeproc on each ui refresh.
0a54596
@takeoverjp takeoverjp mentioned this issue Feb 16, 2021
Merged
takeoverjp added a commit to takeoverjp/nethogs that referenced this issue Feb 17, 2021
@takeoverjp
Issue: raboof#96 - Garbage collect inodeproc once every 50 ui refresh…
b97fb4c 
… 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`.
raboof added a commit that referenced this issue Feb 17, 2021
@raboof
Merge pull request #203 from takeoverjp/feature-garbage-collect-inode…
06fdccb 
…proc

Issue: #96 - Garbage collect inodeproc on each ui refresh.
@raboof
Copy link
Owner

raboof commented Feb 17, 2021

Likely fixed by #203 , feel free to open a new issue when you encounter a leak after this change

@raboof raboof closed this as completed Feb 17, 2021
daler-rahimov pushed a commit to daler-rahimov/nethogs that referenced this issue Jan 30, 2022
@takeoverjp @daler-rahimov
Issue: raboof#96 - Garbage collect inodeproc on each ui refresh.
d1ce253
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
help wanted long-running-usecase
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@raboof @webzorg @wodencafe @NoSuck and others