-
-
Notifications
You must be signed in to change notification settings - Fork 643
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 leaks #731
Comments
The old codebase version 1.9.1 doesn't seem to leak memory and currently I'm using that as a workaround. |
Thank you so much for this!! I'd tried in vain to get Valgrind working on Mac so thanks for bringing this tool up. Can address this much quicker now 👍👍👍 |
Thanks to your amazing work, this will be fixed in #736 |
Confirmed that this issue is resolved in release v2.1.0-beta. Thanks a lot for your help and time. |
xbar version: v2.0.42-beta
macOS version: 10.15.7
Starting xbar up, it uses about 40MB. Running for a few minutes, it builds up to 50MB. Left unchecked for hours, it ended up using multiple GBs which eventually caught my attention.
Running Instruments' Leaks tool on the process shortly after startup yields thousands of small leaks over a roughly two-minute time span. The majority of the leaks stem from
CreateMenuItemCallbackData
:I removed all of my scripts to narrow down the scope of the problem, left only the following script running as
foo.2s.sh
, and the leak persisted:I don't know whether this problem is new or a regression since I've only started using xbar recently.
I've checked the following versions and the leaks are present in all of them:
The text was updated successfully, but these errors were encountered: