Ticket #211 (closed defect: invalid)

Opened 4 years ago

Last modified 4 years ago

bluetooth headset makes cpu go to 100%

Reported by: jbrnd Owned by: lennart
Milestone: Component: daemon
Keywords: Cc:

Description

I'm using PulseAudio 0.9.8 on Ubuntu kernel 2.6.24-2-generic, along with bluez version 3.24.

If I load Pulse without any bluetooth lines in /etc/pulse/default.pa, everything works normally. However, when I add

load-module module-alsa-sink device=head_blz sink_name=head_pulse load-module module-alsa-source device=head_blz source_name=head_pulse_src

then CPU usage goes to 100% immediately on Pulse startup, even if no sound is playing. Pulse still works and plays the sound, though. The ~/.asoundrc that defines the head_blz device is

pcm.head_blz_hw {

type bluetooth device XX:XX:XX:XX:XX:XX

}

ctl.head_blz {

type bluetooth device XX:XX:XX:XX:XX:XX

}

pcm.head_blz {

type plug slave.pcm "head_blz_hw"

}

pcm.pulse {

type pulse

}

ctl.pulse {

type pulse

}

If I attach gdb to pulse at 100% cpu usage, I get a backtrace like

0x00002b29e9bedaa6 in poll () from /lib/libc.so.6 (gdb) bt #0 0x00002b29e9bedaa6 in poll () from /lib/libc.so.6 #1 0x00002b29e82dd2bc in pa_mainloop_poll () from /usr/lib/libpulsecore.so.5 #2 0x00002b29e82de108 in pa_mainloop_iterate ()

from /usr/lib/libpulsecore.so.5

#3 0x00002b29e82de1a0 in pa_mainloop_run () from /usr/lib/libpulsecore.so.5 #4 0x000000000040752d in main ()

Attachments

bt (388 bytes) - added by jbrnd 4 years ago.
Non-mangled backtrace

Change History

Changed 4 years ago by jbrnd

  • attachment bt added

Non-mangled backtrace

Changed 4 years ago by lennart

  • status changed from new to closed
  • resolution set to invalid

Sorry, this is an issue in the BlueZ plugin for ALSA, not in PA. Please report this to the BlueZ people if it still is a problem with their newest release.

Note: See TracTickets for help on using tickets.