Bug 161828 - knotify4 process consumes > 90% CPU after upgrade to 4.04
Summary: knotify4 process consumes > 90% CPU after upgrade to 4.04
Status: RESOLVED WORKSFORME
Alias: None
Product: kdelibs
Classification: Unmaintained
Component: knotify (show other bugs)
Version: 4.0
Platform: Compiled Sources Linux
: NOR crash
Target Milestone: ---
Assignee: Olivier Goffart
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-05-09 01:46 UTC by jamese
Modified: 2011-05-12 16:12 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description jamese 2008-05-09 01:46:40 UTC
Version:           4.04 (using Devel)
Installed from:    Compiled sources
OS:                Linux

I've upgraded to KDE 4.04 using the Kubuntu Hardy Backports repo (instructions on kubuntu.org). On logging in, the process knotify4 is consuming > 90% CPU. An strace produces this:

clock_gettime(CLOCK_MONOTONIC, {4360, 740387967}) = 0
clock_gettime(CLOCK_MONOTONIC, {4360, 740410876}) = 0
read(8, 0x807934c, 4096)                = -1 EAGAIN (Resource temporarily unavailable)
poll([{fd=3, events=POLLIN}, {fd=9, events=POLLIN}, {fd=8, events=POLLIN}, {fd=5, events=POLLIN}, {fd=13, events=POLLIN}], 5, 0) = 0
read(8, 0x807934c, 4096)                = -1 EAGAIN (Resource temporarily unavailable)
clock_gettime(CLOCK_MONOTONIC, {4360, 740501676}) = 0
clock_gettime(CLOCK_MONOTONIC, {4360, 740524586}) = 0
read(8, 0x807934c, 4096)                = -1 EAGAIN (Resource temporarily unavailable)
poll([{fd=3, events=POLLIN}, {fd=9, events=POLLIN}, {fd=8, events=POLLIN}, {fd=5, events=POLLIN}, {fd=13, events=POLLIN}], 5, 0) = 0
read(8, 0x807934c, 4096)                = -1 EAGAIN (Resource temporarily unavailable)
clock_gettime(CLOCK_MONOTONIC, {4360, 740615106}) = 0
clock_gettime(CLOCK_MONOTONIC, {4360, 740638016}) = 0
read(8, 0x807934c, 4096)                = -1 EAGAIN (Resource temporarily unavailable)
poll([{fd=3, events=POLLIN}, {fd=9, events=POLLIN}, {fd=8, events=POLLIN}, {fd=5, events=POLLIN}, {fd=13, events=POLLIN}], 5, 0) = 0
read(8, 0x807934c, 4096)                = -1 EAGAIN (Resource temporarily unavailable)
clock_gettime(CLOCK_MONOTONIC, {4360, 740728257}) = 0
clock_gettime(CLOCK_MONOTONIC, {4360, 740751167}) = 0
read(8, 0x807934c, 4096)                = -1 EAGAIN (Resource temporarily unavailable)
poll([{fd=3, events=POLLIN}, {fd=9, events=POLLIN}, {fd=8, events=POLLIN}, {fd=5, events=POLLIN}, {fd=13, events=POLLIN}], 5, 0) = 0
read(8, 0x807934c, 4096)                = -1 EAGAIN (Resource temporarily unavailable)
clock_gettime(CLOCK_MONOTONIC, {4360, 740841687}) = 0
clock_gettime(CLOCK_MONOTONIC, {4360, 740864597}) = 0
read(8, 0x807934c, 4096)                = -1 EAGAIN (Resource temporarily unavailable)
poll([{fd=3, events=POLLIN}, {fd=9, events=POLLIN}, {fd=8, events=POLLIN}, {fd=5, events=POLLIN}, {fd=13, events=POLLIN}], 5, 0) = 0
read(8, 0x807934c, 4096)                = -1 EAGAIN (Resource temporarily unavailable)
clock_gettime(CLOCK_MONOTONIC, {4360, 740955117}) = 0
clock_gettime(CLOCK_MONOTONIC, {4360, 740978027}) = 0

ad nauseam

Something to do with the clock plasmoid ? not sure..

I have to kill the process so that my system returns to normal load usage. I searched for similar bugs but found none.

Is there any other info needed ?
Comment 1 jamese 2008-05-09 01:47:52 UTC
Note that the bug notes say compiled from sources, which is not the case. KDE is installed using Kubuntu packages from their repo. Also, 4.04 does not appear in the version info when starting a bug report.
Comment 2 Kubuntiac 2008-05-25 19:45:42 UTC
I'm also getting this bug, also on Kubuntu Hardy (Remix) with KDE 4.04 (installed from Kubuntu packages). Knotify4 seems to frequently chew 50-90% of CPU resources until killed whereafter it works fine (after being restarted).

Let me know if there's something I can provide to help.
Comment 3 Mika Tikka 2008-07-05 17:20:42 UTC
Similar knotify4 activity here (90-99% CPU usage in top), after doing update on Fedora 9 from KDE 4.0.5 to 4.0.84 and re-login.
Comment 4 Cameron Maxwell 2008-11-03 12:00:44 UTC
I experienced similar knotify4 behaviour on the latest KDE4 SVN trunk under Gentoo.  After a short period of time knotify4 would jump to being CPU live locked.  

With a little bit of checking I found that knotify4 was complaining about Phonon not being installed.  Which it wasn't, due to the split ebuild approach under Gentoo.

After installing Phonon I have found knotify4 has run for several hours without any console output or becoming CPU intensive.


Console output of knotify4 when Phonon not installed:
---------------------------------------
knotify(7613)/kdecore (trader) KServiceTypeTrader::defaultOffers: KServiceTypeTrader: serviceType  "PhononBackend"  not found
WARNING: bool Phonon::FactoryPrivate::createBackend() phonon backend plugin could not be loaded
QFSFileEngine::open: No file name specified
QFile::seek: IODevice is not open
QFSFileEngine::open: No file name specified
QFile::seek: IODevice is not open
QFSFileEngine::open: No file name specified
QFile::seek: IODevice is not open
QFSFileEngine::open: No file name specified
QFile::seek: IODevice is not open
QFSFileEngine::open: No file name specified
QFile::seek: IODevice is not open
QFSFileEngine::open: No file name specified
QFile::seek: IODevice is not open
QFSFileEngine::open: No file name specified
QFile::seek: IODevice is not open
QFSFileEngine::open: No file name specified
knotify(7613)/kdecore (trader) KServiceTypeTrader::defaultOffers: KServiceTypeTrader: serviceType  "PhononBackend"  not found
Comment 5 Dario Andres 2009-01-09 17:48:26 UTC
Have you experienced this bug again using a recent KDE (4.1.3 / 4.1.4 / 4.2beta2 / 4.2rc1 / 4.2svn) ? Thanks :)
Comment 6 jamese 2009-01-12 00:09:52 UTC
No, only initially then it did not repeat itself.
Comment 7 Manuel Amador (Rudd-O) 2009-07-21 11:20:55 UTC
Sorry, you need to reopen this because I experience this with KDE 4.3rc2, PulseAudio sound server output device, Phonon-Xine backend.
Comment 8 Manuel Amador (Rudd-O) 2009-07-21 11:23:08 UTC
sorry I meant gstreamer backend
Comment 9 Rob Wilmshurst 2011-05-12 16:12:51 UTC
Maybe caused by http://bugs.kde.org/156215