Summary: | Kmix taking to much cpu resources | ||
---|---|---|---|
Product: | [Applications] kmix | Reporter: | Leo <sir_kalot> |
Component: | general | Assignee: | Christian Esken <esken> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | bjoern, incarus6 |
Priority: | NOR | ||
Version: | 3.7 | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: |
Systemmonitor. Note: 25% CPU on Quadcore is 100% at one core
Graphic of CPU usage |
Description
Leo
2011-02-11 11:29:12 UTC
Same for me. Kmix (and kded4) taking 100% of one of my cpu's (Quad-core). It seems to be related with "activities", because it happens when I'm messing around with the activity settings. Try to delete all unnecessary activities and recreate your current, that should temporary fix it, but it's not a permanent solution. Bug Priority should be "Critical" (crashes, loss of data, severe memory leak). Created attachment 57210 [details]
Systemmonitor. Note: 25% CPU on Quadcore is 100% at one core
Created attachment 57211 [details]
Graphic of CPU usage
I can kill kmix and start it again, but the new kmix process is hanging too. Output: chris@Linux:~$ kmix Bus::open: Can not get ibus-daemon's address. IBusInputContext::createInputContext: no connection to ibus-daemon unnamed app(6376): Communication problem with "kmix" , it probably crashed. Error message was: "org.freedesktop.DBus.Error.NoReply" : " "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken." " Duplicate of Bug 264292 *** This bug has been marked as a duplicate of bug 264292 *** |