[pulseaudio-tickets] [PulseAudio] #758: High CPU load with mixers as `gnome-volume-control.pulse` and `pavucontrol`.

[PulseAudio]

#758: High CPU load with mixers as `gnome-volume-control.pulse` and
`pavucontrol`.
--------------------------+-------------------------------------------------
  Reporter:  PaulePanter  |       Owner:  lennart
      Type:  defect       |      Status:  new    
 Milestone:               |   Component:  daemon 
Resolution:               |    Keywords:         
--------------------------+-------------------------------------------------

Comment(by PaulePanter):

 Replying to [comment:8 PaulePanter]:
 > Replying to [comment:3 PaulePanter]:
 > > Replying to [comment:2 PaulePanter]:
 > > > Replying to [comment:1 lennart]:
 > > > > A per symbol breakdown would be good.
 > > >
 > > > What options do I have to pass to `opreport` to get such a symbol
 breakdown?
 > > >
 > > > I searched for this »oprofile "symbol breakdown"« and the hits did
 not contain any information on what options to use. Reading the manual
 page (`man opreport`) and searching for »symbol« also just brought the
 `-l` option to my attention.
 > >
 > > I just read HowToUseOProfile again were it says in step 5 »Generate a
 per-symbol break down of the profile data:« to use `opreport -l
 /usr/bin/pulseaudio` whose output I provided in my report. Or did I do
 anything wrong. I have the package with debug symbols installed
 (pulseaudio-dbg 0.9.21-1).
 >
 > Could you please point me to some instruction on how to generate the
 information you need.

 Thanks to Ford_Perfect on the IRC channel, it was pointed out to me, that
 there seems to be some problems with the debugging symbols. I try to
 straighten this out [1] and will submit the OProfile symbol breakdown
 afterward.

 [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=565373

-- 
Ticket URL: <http://pulseaudio.org/ticket/758#comment:9>
PulseAudio <http://pulseaudio.org/>
The PulseAudio Sound Server