Bug#771105: pulseaudio: Loops on daemon respawn

Felipe Sateler fsateler at debian.org
Tue Dec 2 16:36:42 UTC 2014


On Wed, Nov 26, 2014 at 6:41 PM, David Lynam
<david.lynam at redbrick.dcu.ie> wrote:
> If I have Clementine open and it's trying to play something while stuck, it will get to about 10% CPU.
> If GNOME Shell is the cause (for example, if I hold down the volume
> change key combination), this reaches about 5% CPU.
>
> During YouTube playback, Iceweasel gets to 13-15% CPU.
>
> For a few seconds during the start of the loop, two Pulseaudio processes
> will reach 3-5% CPU each, then die down a bit.
>
> However, if I trigger this with a volume change, a few seconds later I
> can still hear the looping and GNOME Shell is a bit unresponsive, but
> none of the processes in question register >0.0% CPU usage.
>
> I added tsched=0 because I was getting horrific distortion and echoing
> from the likes of Google Hangouts. I thought timer-based scheduling was
> on by default and tsched=0 enables the older, interrupt-based
> scheduling.

Yes, you are correct. Sorry about that. Does the problem happen if you
enable timer scheduling?

>
> Log is attached. The problem is present from the very start of the
> process. In it, I:
>
> - change volume via GNOME shell
> - play a song in Clementine (and kill Clementine)
> - play a sound in Iceweasel
> - play a YouTube video in Iceweasel (uses non-free Flash)

Something is trying to move the volume a lot. This is strange.



-- 

Saludos,
Felipe Sateler



More information about the pkg-pulseaudio-devel mailing list