Bug 266070

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

Version:           3.7 (using KDE 4.6.0) 
OS:                Linux

After some time using my pc, I noticed that kmix takes almos 100% of a cpu, the pc slowes down, and it is "impossible" slow use the plasma interface

Reproducible: Sometimes

Steps to Reproduce:
Just use the pc

Actual Results:  
1 cpu to 100% usage, unpossible to access to the kmix plasma panel and modify the volume

Comment 1 incarus6 2011-02-13 13:32:14 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).

Comment 2 incarus6 2011-02-13 13:37:08 UTC

Created attachment 57210 [details]
Systemmonitor. Note: 25% CPU on Quadcore is 100% at one core

Comment 3 incarus6 2011-02-13 13:37:59 UTC

Created attachment 57211 [details]
Graphic of CPU usage

Comment 4 incarus6 2011-02-13 13:54:31 UTC

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." "

Comment 5 incarus6 2011-02-13 14:06:53 UTC

Duplicate of Bug 264292

Comment 6 Björn Ruberg 2011-03-27 22:43:23 UTC


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