-
Notifications
You must be signed in to change notification settings - Fork 94
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
High CPU Usage even if unused #10
Comments
Hmmm, Approaches I could think of are:
Maybe its even GLib responding unnecessarily to something. Personally I never experienced (or noticed) that issue since I use the Pi exclusively for bluetooth in my project. |
I am experiencing this as well. It seems to happen shortly after the first bluetooth disconnect after a boot; at least for me. I'm running bt-speaker on a RPi 3 using an up-to-date retropie image (installed retropie 4.2, then updated setup script and retropie packages using retropie's updater). Also using ethernet, wifi is disabled via /boot/config.txt; I am using the onboard bluetooth however. |
Restarting bt_speaker resolves the issue immediately. I can confirm that it happens after disconnecting. Nevertheless the service seems to work fine, even with high cpu usage. |
I can confirm it now. Will definitely look into this and try to fix it tonight or tomorrow. It looks like the |
n1, will validate your changes soon. Thanks |
Turns out that bluez does not tell to release the filedescriptor of the audio stream on disconnect and the GObject listener went crazy. It should be fixed now. |
Confirmed fixed for me (retropie 4.2 base image, packages all up-to-date as of 2017-07-16). Thanks!! Working great :-) |
confirmed - Thanks! |
Hi all,
I recognized an issue in a RPI3 using bt speaker to use the Pi as an audio transceiver. First of all, bt-speaker is working fine without problems. I do not use the builtin WLAN module to avoid the sound problems.
After some time, even if not used, the python-process of bt-speaker constantly causes high cpu usage (100% on one core). How can I help to investigate?
Regards,
The text was updated successfully, but these errors were encountered: