-
-
Notifications
You must be signed in to change notification settings - Fork 189
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] Abnormal CPU usage #515
Comments
I fixed this recently, but I haven't released a new stable release for it yet. |
Also have this issue on Arch. Good to know there's a fix! |
The fix has been released in v5.0.1: https://github.com/timschneeb/GalaxyBudsClient/releases/tag/5.0.1 |
I've been running 5.0.1 on Linux for a couple days and the 100% CPU bug does not seem to be fixed. Keeps one of my cores pegged constantly. If you would like debug data, please let me know what you'd like to see. |
I found a deadlock in one of the UI libraries I'm using. Downgrading it (commit ab5f349) appears to have
Edit: Looks like the actual issue is caused by a library used to create global keyboard hooks on X11. It only spikes the CPU usage after running for 1 or 2 hours, making debugging this annoying. |
Fixed by TolikPylypchuk/SharpHook#112 and b3c741b Binaries with the fix can be downloaded here for now: https://github.com/timschneeb/GalaxyBudsClient/actions/runs/9922666656 |
Thanks for looking into this @timschneeb. I'll give it a test drive later today. Since I'm running Nvidia, I haven't tested this with Wayland yet, but hopefully this fixes it for X11. |
Describe the bug
Idle in background uses about 8% cpu which doesn't sound right (not sure what the old version had) but when disconnecting and reconnecting my buds 2 pro while the application is running the CPU usages goes up to 16% and stays there until you completely close and re open it again
To Reproduce
Run application in background. disconnect earbuds and reconnect.
Expected behavior
No permanent doubling of the CPU usage.
Screenshots
Desktop (please complete the following information):
Additional context
Log files
application.log
The text was updated successfully, but these errors were encountered: