'Twas brillig, and Lennart Poettering at 10/08/09 19:41 did gyre and gimble:
On Mon, 10.08.09 12:24, Colin Guthrie ([email protected]) wrote:

Hi,

Anyone noticed this?

The CPU usuage of g-s-d and g-v-c-a going through the roof (with PA following it).

Seems to be getting stuck in some kind of loop.

I have to kill both g-v-c-a and g-s-d to get things back to normal.

g-v-c-a? I onlyknow g-v-c, What's that -a about?

gnome-volume-control-applet

i.e. the little thingy in the tray to control the volume.

Smells like one of those g-v-c feedback loops. i.e. user triggers
volume change, g-v-c forwards that to PA. PA informs all clients about
the vol change including g-v-c. g-v-c forwards that to gtk. gtk
informs g-v-c about the changes it just made to the UI, pavucontrol
forwards that to PA, GOTO 10.

Under no circumstances g-v-c should forward anything coming in from
PA back to PA. And under no circumstances g-v-c should forward
anything coming from gtk back to gtk. As it stands now this is however
broken in g-v-c.

A while back I sat down and fixed a couple of those issues, but I
think there are a number of issues left.

Please file bugs against g-v-c regarding this.

Sure I'll try and write it up and work out a trigger too.

Col

--

Colin Guthrie
gmane(at)colin.guthr.ie
http://colin.guthr.ie/

Day Job:
  Tribalogic Limited [http://www.tribalogic.net/]
Open Source:
  Mandriva Linux Contributor [http://www.mandriva.com/]
  PulseAudio Hacker [http://www.pulseaudio.org/]
  Trac Hacker [http://trac.edgewall.org/]

_______________________________________________
pulseaudio-discuss mailing list
[email protected]
https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss

Reply via email to