-
Notifications
You must be signed in to change notification settings - Fork 298
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
Potential Memory Leak #151
Comments
Can you confirm you're running the latest version (0.9.16)? We're trying to reproduce but none of our machines seem to have unexpectedly high memory use. We think it could be due to fast-user-switching which we don't really use but Santa is designed to support. A recent commit (5e4b835), which hasn't yet been included in a release could have inadvertently fixed this but we'd like to reproduce to confirm. |
Could you also provide your config?
|
@russellhancox Having said that, the first 3 entries in that table were running 0.9.16, so although it's a smaller sample size, might still be the case. Also found another one running 0.9.16, uptime 28days, Santa using 1.8GB. @tburgin
Currently, we've just left Santa in the default MONITOR mode, and been adding items to the blacklist by sending a payload-free package containing 4 santactl commands |
Thanks, I am still unable to reproduce the issue. When you come across a machine that is in this state can you grab a memory graph and share it here?
|
Yeah, that would be great. |
It turns out when running without a config both binaries will leak around 24 bytes every 200ms.
Fixed in #154 |
I recently noticed a proportional trend between Santa app and santad's memory usage and a mac's uptime.
I've looked at multiple macs in our fleet (running 10.10/10.11/10.12) and it appears to be consistent with throughout.
We're running Santa pretty lightweight, Default configuration with 4 blacklisted binaries (OS X Installers)
Example of the uptime/usage trend:
Let me know if there's anything else I can provide to help
The text was updated successfully, but these errors were encountered: