[Konsole-devel] [Bug 189756] Konsole: High CPU caused by e.g. mplayer or mencoder status updates

Hugo.Mildenberger at namir.de Hugo.Mildenberger at namir.de
Wed Oct 28 11:13:37 UTC 2009


https://bugs.kde.org/show_bug.cgi?id=189756


Hugo.Mildenberger at namir.de changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |Hugo.Mildenberger at namir.de




--- Comment #4 from  <Hugo Mildenberger namir de>  2009-10-28 12:13:36 ---
I observed a very similar behaviour using kde-4.3.2, when running for instance
htop or top within "konsole": constantly 10% cpu load (sometimes, under yet
unknown circumstances even about 50%, also constantly), whereas running "top"
within xterm yields in max. 1% cpu load. The same holds true when running top
within a native console. However, in my environment, it is not "konsole"
itself, but "X" which consumes that much. The CPU-load clearly depends on
whether "konsole" runs "top". It does not depend on "konsole" window being
active, minimized or even moved to another desktop. The system has Compositing
enabled. Looking for a difference, I noticed that xterm uses libxcb, while
"konsole" does not.

-- 
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 konsole-devel mailing list