[Bug 1091752] New: pulseaudio shows constant 18% cpu when kontact is running
http://bugzilla.suse.com/show_bug.cgi?id=1091752 Bug ID: 1091752 Summary: pulseaudio shows constant 18% cpu when kontact is running Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE Applications Assignee: opensuse-kde-bugs@opensuse.org Reporter: robby.engelmann@igfs-ev.de QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- My first guess for that would be the text-to-speech module? 1. Start Kontact --> see pulseaudio draw cpu power 2. Close Kontact --> see pulseaudio cpu dropping after 2-5 sec. Can anybody confirm that? I am using latest TW snapshot. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1091752
http://bugzilla.suse.com/show_bug.cgi?id=1091752#c1
Wolfgang Bauer
http://bugzilla.suse.com/show_bug.cgi?id=1091752
http://bugzilla.suse.com/show_bug.cgi?id=1091752#c2
Robby Engelmann
http://bugzilla.suse.com/show_bug.cgi?id=1091752
http://bugzilla.suse.com/show_bug.cgi?id=1091752#c3
--- Comment #3 from Wolfgang Bauer
yes, this helps. Before killing speech-dispatcher the pulseaudio process is draining cpu, after that not any more.
Well, then it is indeed related to the text-to-speech feature. No idea whether it's a problem in KDEPIM, qt5-qttexttospeech, speech-dispatcher or espeak though. I don't see constant CPU usage here (without PulseAudio), although I just noticed that speech-dispatcher does block the sound card constantly while kmail is running (might be a configuration problem though). Maybe we should disable that again? Unfortunately there's no way to make it optional, either you build it with speech support or without. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1091752
http://bugzilla.suse.com/show_bug.cgi?id=1091752#c4
Fabian Vogt
(In reply to Robby Engelmann from comment #2)
yes, this helps. Before killing speech-dispatcher the pulseaudio process is draining cpu, after that not any more.
Well, then it is indeed related to the text-to-speech feature. No idea whether it's a problem in KDEPIM, qt5-qttexttospeech, speech-dispatcher or espeak though.
I don't see constant CPU usage here (without PulseAudio), although I just noticed that speech-dispatcher does block the sound card constantly while kmail is running (might be a configuration problem though).
Maybe we should disable that again?
Unfortunately there's no way to make it optional, either you build it with speech support or without.
We can - speech-dispatcher is just one of the backends. If we remove the recommends (if it got installed because of our recommends), it won't be installed by default anymore. The question is why the backend got started even though it's not used though. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1091752
http://bugzilla.suse.com/show_bug.cgi?id=1091752#c6
--- Comment #6 from Robby Engelmann
Maybe it would help to delete the speech-dispatcher config (/etc/speech-dispatcher/speechd.conf) and reinstall the package to recreate the default one? (maybe speech-dispatcher is blocking PA from accessing the sound card because it's configured to not use PA, causing it to try again and again resulting in CPU usage, but I cannot reproduce it that way either)
Or maybe there are some "special" pulseaudio plugins installed that might trigger this? (the equalizer e.g.)
deinstallation of speech-dispatcher and removal of etc/speech-dispatcher/ plus reinstall it did not help here. The problem is back after speech-dispatcher is pulled in by zypper dup. I only have the standard pa-plugins installed, nothing added by hand. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com