Bug 57522 - pavucontrol causing heavy Xorg load when running for a long time
Summary: pavucontrol causing heavy Xorg load when running for a long time
Status: RESOLVED MOVED
Alias: None
Product: PulseAudio
Classification: Unclassified
Component: pavucontrol (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium major
Assignee: pulseaudio-bugs
QA Contact: pulseaudio-bugs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-11-25 16:41 UTC by Raphael Michel
Modified: 2018-07-30 09:31 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments

Description Raphael Michel 2012-11-25 16:41:13 UTC
I normally have pavucontrol running in background all the time. At least since pavucontrol 1.0 (as shipped with Ubuntu 12.10, but maybe for longer) the process /usr/bin/X starts consuming 98% CPU when pavucontrol is running for some time. I observe this value going down to normal levels as soon as I kill pavucontrol. I'm pretty sure this should not happen. Is it possible that it is a bug in pavucontrol and if yes, what information can I provide to help debugging?
Comment 1 Tanu Kaskinen 2012-11-26 14:05:04 UTC
It's possible that pavucontrol does something that it shouldn't do.

How long do you have to wait until the problem happens? Does pavucontrol CPU use go up too?

Does the X CPU use go up after some specific event? If you don't know, are you able to make a small program/script that monitors the X CPU consumption and alerts you immediately when it starts to look unhealthy?
Comment 2 GitLab Migration User 2018-07-30 09:31:03 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/pulseaudio/pavucontrol/issues/42.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.