[pulseaudio-tickets] [PulseAudio] #758: High CPU load with mixers as `gnome-volume-control.pulse` and `pavucontrol`.
PulseAudio
trac-noreply at tango.0pointer.de
Thu Jan 14 15:25:58 PST 2010
#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: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.
--
Ticket URL: <http://pulseaudio.org/ticket/758#comment:8>
PulseAudio <http://pulseaudio.org/>
The PulseAudio Sound Server
More information about the pulseaudio-bugs
mailing list