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.

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

[BUG] memory leak #912

Open
nnym opened this issue Aug 15, 2024 · 0 comments
Open

[BUG] memory leak #912

nnym opened this issue Aug 15, 2024 · 0 comments
Assignees
Labels
bug Something isn't working

Comments

@nnym
Copy link

nnym commented Aug 15, 2024

Describe the bug

Btop leaks RAM continuously while running: on startup RSS is ~23M and over ~60 days with update interval 1000 ms it leaked over 500M. Around that point it became very slow and crashed after a few key presses.

btop-rss

Most increments are of 160 B.

To Reproduce

  1. Run btop.
  2. Wait a while.

Expected behavior

Since btop retains a fixed amount of statistics, its RSS should remain close to its initial value.

Info

  • btop++ version: 1.3.2
  • Binary: from Arch Linux's official extra repository which builds from source
  • Architecture: x86_64
  • Platform: Linux
  • (Linux) Kernel: 6.9.3-arch1-1
  • Terminal used: Alacritty
  • Font used: FiraCode Nerd Font Mono

Additional context

2024/08/10 (05:12:37) | ===> btop++ v.1.3.2
2024/08/10 (05:12:37) | DEBUG: Running in DEBUG mode!
2024/08/10 (05:12:37) | INFO: Logger set to DEBUG
2024/08/10 (05:12:37) | DEBUG: Setting LC_ALL=en_US.UTF8
2024/08/10 (05:12:37) | INFO: Running on /dev/pts/1
2024/08/10 (05:12:37) | INFO: Failed to load librocm_smi64.so, AMD GPUs will not be detected: librocm_smi64.so.6: cannot open shared object file: No such file or directory
2024/08/10 (05:12:37) | DEBUG: Shared::init() : Initialized.
2024/08/13 (22:01:37) | INFO: Quitting! Runtime: 3d 16:49:00
@nnym nnym added the bug Something isn't working label Aug 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants