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

Massive memory footprint #40

Open
yik77 opened this issue Feb 1, 2021 · 3 comments
Open

Massive memory footprint #40

yik77 opened this issue Feb 1, 2021 · 3 comments
Labels
bug Something isn't working

Comments

@yik77
Copy link

yik77 commented Feb 1, 2021

First, I love pibar and would like to thank its author(s). Great work. Goes nicely with pihole. Now back to the issue:

I see huge memory usage for tiny program than produces few lines of text. Over time, when my mac is running and running, the size of memory used by pibar is almost 2 GB. This is not normal

I am attaching screenshot:
Pibar

I am running OS X High Sierra, 10.13.6 on MPB with 8 GB of RAM. My typical uptime is in months.

@amiantos
Copy link
Owner

amiantos commented Feb 1, 2021

Hmm.. I have never seen this happen personally (and I've been running PiBar all day every day since release) and haven't heard this complaint elsewhere. What's your configuration look like? I really can't imagine why this would happen, as the app isn't really storing much of anything in memory...

@yik77
Copy link
Author

yik77 commented Feb 1, 2021

I would say relatively typical one.
piholes
running 2 piholes on 2 pi zero w boards, none of which is DHCP server, home network with 15 or so devices at max, comcast cable for internet, plain vanilla configuration of blacklists, no whitelists.

I'll be happy to do more to troubleshoot this issue. It is reproducible, not once-and-never-again.

@amiantos
Copy link
Owner

amiantos commented Feb 1, 2021

When I start working on it again I'll try to do a code audit and some theorizing on where there could be a memory leak. Maybe it's somehow related to High Sierra, but I'd be surprised. Either way, I will keep this in mind and try to track down possible culprits.

@amiantos amiantos added the bug Something isn't working label Feb 1, 2021
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