[kwin] [Bug 366742] Qbitorrent Xorg/kwin_x11 high cpu usage while adding more than 1 torrent at the same time.

https://bugs.kde.org/show_bug.cgi?id=366742 Tony changed: What|Removed |Added Resolution|--- |INVALID Status|UNCONFIRMED

[kwin] [Bug 366742] Qbitorrent Xorg/kwin_x11 high cpu usage while adding more than 1 torrent at the same time.

https://bugs.kde.org/show_bug.cgi?id=366742 --- Comment #9 from Tony --- I did as you said, suspended the compositor, removed qbitorrent icon from notification area. Like this, it does not happen right away as i said before, it only takes longer to pop up, have to force it

[kwin] [Bug 366742] Qbitorrent Xorg/kwin_x11 high cpu usage while adding more than 1 torrent at the same time.

https://bugs.kde.org/show_bug.cgi?id=366742 --- Comment #8 from Thomas Lübking --- 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

[kwin] [Bug 366742] Qbitorrent Xorg/kwin_x11 high cpu usage while adding more than 1 torrent at the same time.

https://bugs.kde.org/show_bug.cgi?id=366742 --- Comment #7 from Tony --- For that bactrace no i did not. But it happens in any case compositing on/off, the only difference is that when off i does not happen right away i need to move the windows around, click on them or wait a

[kwin] [Bug 366742] Qbitorrent Xorg/kwin_x11 high cpu usage while adding more than 1 torrent at the same time.

https://bugs.kde.org/show_bug.cgi?id=366742 --- Comment #6 from Martin Gräßlin --- thanks. The backtrace is directly from the event loop when processing X11 events. That could confirm the hypothesis Thomas had in comment #2. Did you try with just turning compositing off? --

[kwin] [Bug 366742] Qbitorrent Xorg/kwin_x11 high cpu usage while adding more than 1 torrent at the same time.

https://bugs.kde.org/show_bug.cgi?id=366742 --- Comment #5 from Tony --- Ok, i gave it another try. Had to read about gdb a bit The desktop still locks while using gdb though so here is what i did: First i delete .config and .cache from "home" and start the desktop clean.

[kwin] [Bug 366742] Qbitorrent Xorg/kwin_x11 high cpu usage while adding more than 1 torrent at the same time.

https://bugs.kde.org/show_bug.cgi?id=366742 --- Comment #4 from Martin Gräßlin --- for gdb you need to go to another VT. Never gdb from the running session. Sorry, forgot to mention that. -- You are receiving this mail because: You are watching all bug changes.

[kwin] [Bug 366742] Qbitorrent Xorg/kwin_x11 high cpu usage while adding more than 1 torrent at the same time.

https://bugs.kde.org/show_bug.cgi?id=366742 --- Comment #3 from Tony --- Sadly can't provide a proper backtrace When i try to do it as non-root i get "ptrace: Operation not permitted." Using sudo + having the compositor on, gdb won't even open on the terminal and the

[kwin] [Bug 366742] Qbitorrent Xorg/kwin_x11 high cpu usage while adding more than 1 torrent at the same time.

https://bugs.kde.org/show_bug.cgi?id=366742 --- Comment #2 from Thomas Lübking --- > Xorg and kwin_x11 Smells like something (qbittorrent? plasmashell?) will cause massive repaints. Suspend the compositor (SHIFT+Alt+F12) and check the remaining load on Xorg plus

[kwin] [Bug 366742] Qbitorrent Xorg/kwin_x11 high cpu usage while adding more than 1 torrent at the same time.

https://bugs.kde.org/show_bug.cgi?id=366742 --- Comment #1 from Martin Gräßlin --- could you please install debug symbols for KWin and gdb into the kwin process with the high cpu usage and then provide us a backtrace of it? That should be something like: 1. ps -AF | grep