Bug 87566

Summary:	pavucontrol 2.0 using 100% CPU after machine suspend
Product:	PulseAudio	Reporter:	main.haarp
Component:	pavucontrol	Assignee:	pulseaudio-bugs
Status:	RESOLVED MOVED	QA Contact:	pulseaudio-bugs
Severity:	normal
Priority:	medium	CC:	lennart
Version:	unspecified
Hardware:	Other
OS:	Linux (All)
Whiteboard:
i915 platform:		i915 features:

Description main.haarp 2014-12-21 21:00:05 UTC

If pavucontrol is running when my machine goes into suspend (for a certain amount of time, this doesn't seem to happen if I suspend just 10 seconds), it will be consuming 100% CPU after the resume.

This seems independent of the bug in which Pulseaudio itself consumes 100% CPU after suspend.

Comment 1 Raymond 2014-12-23 01:53:47 UTC

do you mean the timer don't work as expected after suspend and resume cycle ?

pavucontrol seem monitoring the output and input level

Comment 2 main.haarp 2014-12-23 07:09:30 UTC

What timer? I'm not sure what you're talking about.

Both pavucontrol and pulseaudio itself each consume 100% CPU power after resuming from suspend. This goes away when I close pavucontrol.

Comment 3 GitLab Migration User 2018-07-30 09:28:33 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/16.

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.