On Wed, 24.06.09 14:18, Brian J. Murrell (brian at interlinx.bc.ca) wrote: > On Sun, 2009-06-07 at 01:32 +0200, Lennart Poettering wrote: > > > > Hmm, could you try to play around with oprofile a bit to find out > > where exactly PA starts to spin? > > > > http://pulseaudio.org/wiki/HowToUseOProfile > > I tried this. I had to use the --no-vmlinux option: > > $ sudo opcontrol --no-vmlinux > > Then I did: > > $ sudo opcontrol --start > > and then resumed my audio application. Unfortunately it did not put PA > into a loop, so I paused my audio app and did: > > $ sudo opcontrol --stop > > and then > > $ sudo opcontrol --start > > and then resumed my app. Still no CPU eating loop. I had to repeat the > above a few times before PA would again chew the CPU. > > So I let PA and my audio app run for a while chewing the CPU, however: > > $ sudo opreport -l /usr/bin/pulseaudio > > only produces: > > opreport error: basic_string::erase Looks like a bug in your distribution's packages. Please file a bug in your distro's bug tracker and ask them to fix this. Lennart -- Lennart Poettering Red Hat, Inc. lennart [at] poettering [dot] net http://0pointer.net/lennart/ GnuPG 0x1A015CC4
