Bug 33837 - dbus-daemon runaway at 100% CPU
Summary: dbus-daemon runaway at 100% CPU
Status: RESOLVED DUPLICATE of bug 23194
Alias: None
Product: dbus
Classification: Unclassified
Component: core (show other bugs)
Version: 1.4.x
Hardware: x86-64 (AMD64) Linux (All)
: medium critical
Assignee: Havoc Pennington
QA Contact: John (J5) Palmieri
Depends on:
Reported: 2011-02-02 05:57 UTC by Nick Krutiolkin
Modified: 2011-02-02 06:58 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Description Nick Krutiolkin 2011-02-02 05:57:26 UTC
found a bug description which describes my problem exactly:

Frequent problems with dbus-daemon entering a runaway state, consuming 100% of
one core for extended durations. KDE applications fail to open or react in a
timely manner while this is happening. Screensaver never happens.

Steps to Reproduce:

Haven't been able to identify a particular usage pattern. Typically takes several
days to a week to reoccur. Always happens eventually if I stay logged-in for significant periods of time.

Seems linked to login duration. Running KDE apps (or dbus enabled apps)
include: the KDE desktop, Krusader, Konsole. Common non-KDE apps include: Firefox, Chrome, Eclipse, VirtualBox(non-OSE), Pidgin, Skype, Dropbox, System Monitor.

Actual Results:  
One core at sustained 100% cpu. Launcher won't start new applications, usually have to reboot from command line.
Restarting the daemon doesn't seem to have an effect.
While killing it makes the system unusable irrespective of a future daemon restart.

Expected Results:
dbus shouldn't hog CPU
restart dbus should return the KDE env to a viable state after killing the process

Additional Information:
KDE 4.5.1 on Ubuntu
8 GB or RAM (probably unusual)
Comment 1 Thiago Macieira 2011-02-02 06:58:32 UTC
In the absence of a way to reproduce, marking as duplicate of the most likely cause.

*** This bug has been marked as a duplicate of bug 23194 ***

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.