https://bugs.kde.org/show_bug.cgi?id=366742
--- Comment #8 from Thomas Lübking <thomas.luebk...@gmail.com> --- Some static backtrace won't get you anywhere reg. CPU load - this would only work if kwin would be trapped in an infinite loop. Suspend the compositor (SHIFT+Alt+F12), run qbittorrent and watch remaining CPU loads. A high cpu load in qbittorrent and Xorg, but no load in kwin likely means that the client repaints like hell - this will directly impact the compositor (rasing kwin in that regard) If kwin has high cpu load despite a suspended compositor (no shadows, translucency etc!) that would suggest the client causes map/unmap notifications (some window shows/hides) or configure requests. In the latter case I would check on its systray icon (it certainly has one, yesno?) Try to disable such feature in qbittorrent and see what happens. -- You are receiving this mail because: You are watching all bug changes.
