[Bug 275420] New: Sometimes Kontact and dbus-daemon hog two of my 6 cores with 100% each - killing Kontact solves this
Ekkehard Blanz
Ekkehard.Blanz at gmail.com
Sat Jun 11 18:32:15 BST 2011
https://bugs.kde.org/show_bug.cgi?id=275420
Summary: Sometimes Kontact and dbus-daemon hog two of my 6
cores with 100% each - killing Kontact solves this
Product: kontact
Version: 4.4.10
Platform: Ubuntu Packages
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: general
AssignedTo: kdepim-bugs at kde.org
ReportedBy: Ekkehard.Blanz at gmail.com
Version: 4.4.10 (using KDE 4.6.2)
OS: Linux
When Kontact runs for more than a day on my otherwise very stable Kubuntu 11.04
64-bit system, it causes dbus-daemon and itself to hog all the CPU cycles they
can get. Two of my 6 cores are completely pegged at 100%. When I then kill
Kontact, the problem is temporarily solved. Unfortunately, starting Kontact
again will bring me right back to that situation. Sometimes Kontact won't even
start again while dbus-daemon hogs 100% of a core. I have to restart to be
able to run Kontact normally again. Please let me know if there is any other
information I should provide the next time it does that.
Reproducible: Sometimes
Steps to Reproduce:
Let sit Kontact for some time - often happens when I come back to the computer
in the morning.
Actual Results:
Two CPU cores are pegged at 100% - would render a single core machine useless.
Expected Results:
Kontact and dbus-daemon behaving "nice"ly, using less than solid 100% CPU.
OS: Linux (x86_64) release 2.6.38-8-generic
Compiler: cc
--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
More information about the Kdepim-bugs
mailing list