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

[Tony]

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

Tony  changed:

   What|Removed |Added

 Resolution|--- |INVALID
 Status|UNCONFIRMED |RESOLVED

--- Comment #10 from Tony  ---
Recently checking to see if this was fixed or better, with help from someone
that works in "Linux" for a living it was concluded this is not a Kwin nor
Qbitorrent problem but X's.  

The issue is present on different systems and OSs Neon, Fedora Opensuse and
Debian.

This do not happen under Wayland.

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

[Tony via KDE Bugzilla]

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 (opening many torrents).
Kwin and qbitorrent cpu usage only go up when Xorg usage goes up by a lot in
this case. 
So is more like your 1st case.

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

[Thomas Lübking via KDE Bugzilla]

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

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

[Tony via KDE Bugzilla]

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 little with them open.

This is a backtrace i get with compositing off:

#0  0x7f8669d60c74 in QXcbConnection::checkEvent<(anonymous
namespace)::PropertyNotifyEvent> (this=0x23a64c0, checker=)
at qxcbconnection.h:695
#1  QXcbConnection::getTimestamp (this=0x23a64c0) at qxcbconnection.cpp:1467
#2  0x7f8669d812b2 in QXcbNativeInterface::getTimestamp
(this=this@entry=0x239ee10, screen=screen@entry=0x23b8c80) at
qxcbnativeinterface.cpp:413
#3  0x7f8669d82242 in QXcbNativeInterface::nativeResourceForScreen
(this=0x239ee10, resourceString=..., screen=0x23b8420) at
qxcbnativeinterface.cpp:243
#4  0x7f86803a6c90 in QX11Info::getTimestamp() () from
/usr/lib/x86_64-linux-gnu/libQt5X11Extras.so.5
#5  0x7f867f7f7dd9 in KWin::updateXTime () at /workspace/build/utils.cpp:87
#6  0x7f867f827355 in KWin::Client::updateUserTime (this=0x2753740,
time=time@entry=0) at /workspace/build/activation.cpp:706
#7  0x7f867f828472 in KWin::Workspace::activateClient (this=0x24812b0,
c=0x2753740, force=) at /workspace/build/activation.cpp:330
#8  0x7f867e97a0dc in NETRootInfo::event(xcb_generic_event_t*,
QFlags*, QFlags*) ()
   from /usr/lib/x86_64-linux-gnu/libKF5WindowSystem.so.5
#9  0x7f867f80d946 in KWin::Workspace::workspaceEvent (this=0x24812b0,
e=0x7f86653a00f0) at /workspace/build/events.cpp:265
#10 0x7f867db50f0f in QAbstractEventDispatcher::filterNativeEvent
(this=, eventType=..., message=message@entry=0x7f86653a00f0, 
result=result@entry=0x7fff9943a698) at
kernel/qabstracteventdispatcher.cpp:466
#11 0x7f8669d64684 in QXcbConnection::handleXcbEvent
(this=this@entry=0x23a64c0, event=event@entry=0x7f86653a00f0) at
qxcbconnection.cpp:1103
#12 0x7f8669d65300 in QXcbConnection::processXcbEvents (this=0x23a64c0) at
qxcbconnection.cpp:1735
#13 0x7f867db7fad9 in QObject::event (this=0x23a64c0, e=) at
kernel/qobject.cpp:1263
#14 0x7f867e43f89c in QApplicationPrivate::notify_helper (this=, receiver=0x23a64c0, e=0x7f8665022110) at kernel/qapplication.cpp:3799
#15 0x7f867e447296 in QApplication::notify (this=0x7fff9943ad50,
receiver=0x23a64c0, e=0x7f8665022110) at kernel/qapplication.cpp:3556
#16 0x7f867db53da8 in QCoreApplication::notifyInternal2
(receiver=0x23a64c0, event=event@entry=0x7f8665022110) at
kernel/qcoreapplication.cpp:988
#17 0x7f867db5646b in QCoreApplication::sendEvent (event=0x7f8665022110,
receiver=)
at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231
#18 QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0,
event_type=event_type@entry=0, data=0x238cd30) at
kernel/qcoreapplication.cpp:1649
#19 0x7f867dba3dea in QEventDispatcherUNIX::processEvents (this=0x23e5f20,
flags=flags@entry=...) at kernel/qeventdispatcher_unix.cpp:461
#20 0x7f8669dd887d in QUnixEventDispatcherQPA::processEvents
(this=, flags=...) at
eventdispatchers/qunixeventdispatcher.cpp:68
#21 0x7f867db51d9a in QEventLoop::exec (this=this@entry=0x7fff9943ac40,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:210
#22 0x7f867db5a3ac in QCoreApplication::exec () at
kernel/qcoreapplication.cpp:1261
#23 0x7f867de9cdbc in QGuiApplication::exec () at
kernel/qguiapplication.cpp:1639
#24 0x7f867e43f7f5 in QApplication::exec () at kernel/qapplication.cpp:2975
#25 0x7f867ffae206 in kdemain (argc=1, argv=0x7fff9943aed8) at
/workspace/build/main_x11.cpp:466
#26 0x7f867fbf5830 in __libc_start_main (main=0x400710 ,
argc=1, argv=0x7fff9943aed8, init=, fini=, 
rtld_fini=, stack_end=0x7fff9943aec8) at
../csu/libc-start.c:291
#27 0x00400749 in _start ()
Detaching from program: /usr/bin/kwin_x11, process 3126

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

[Martin Gräßlin via KDE Bugzilla]

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?

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

[Tony via KDE Bugzilla]

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.
I login to  VT3 and VT4. In VT4 have top running, VT3 i used it to run gdb.

So i opened 4 torrents with qbitorrent switch to VT4 check that X and kwin are
using a lot cpu power.
Switch to VT3 and ran gdb, set logging on, and ran bt. I got this on from
"gdb.txt" on my home folder:

#0  QVector::detach
(this=0x1470800) at
../../../../include/QtCore/../../src/corelib/tools/qvector.h:384
#1  QVector::end
(this=0x1470800) at
../../../../include/QtCore/../../src/corelib/tools/qvector.h:208
#2  QXcbConnection::processXcbEvents (this=0x14704f0) at
qxcbconnection.cpp:1731
#3  0x7f54ce159ad9 in QObject::event (this=0x14704f0, e=) at
kernel/qobject.cpp:1263
#4  0x7f54cea1989c in QApplicationPrivate::notify_helper (this=, receiver=0x14704f0, e=0x7f54b4a5aef0) at kernel/qapplication.cpp:3799
#5  0x7f54cea21296 in QApplication::notify (this=0x7ffc2242e190,
receiver=0x14704f0, e=0x7f54b4a5aef0) at kernel/qapplication.cpp:3556
#6  0x7f54ce12dda8 in QCoreApplication::notifyInternal2
(receiver=0x14704f0, event=event@entry=0x7f54b4a5aef0) at
kernel/qcoreapplication.cpp:988
#7  0x7f54ce13046b in QCoreApplication::sendEvent (event=0x7f54b4a5aef0,
receiver=)
at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231
#8  QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0,
event_type=event_type@entry=0, data=0x1456d30) at
kernel/qcoreapplication.cpp:1649
#9  0x7f54ce17ddea in QEventDispatcherUNIX::processEvents (this=0x14abdf0,
flags=flags@entry=...) at kernel/qeventdispatcher_unix.cpp:461
#10 0x7f54ba3b287d in QUnixEventDispatcherQPA::processEvents
(this=, flags=...) at
eventdispatchers/qunixeventdispatcher.cpp:68
#11 0x7f54ce12bd9a in QEventLoop::exec (this=this@entry=0x7ffc2242e080,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:210
#12 0x7f54ce1343ac in QCoreApplication::exec () at
kernel/qcoreapplication.cpp:1261
#13 0x7f54ce476dbc in QGuiApplication::exec () at
kernel/qguiapplication.cpp:1639
#14 0x7f54cea197f5 in QApplication::exec () at kernel/qapplication.cpp:2975
#15 0x7f54d0588206 in kdemain (argc=1, argv=0x7ffc2242e318) at
/workspace/build/main_x11.cpp:466
#16 0x7f54d01cf830 in __libc_start_main (main=0x400710 ,
argc=3, argv=0x7ffc2242e318, init=, fini=, 
rtld_fini=, stack_end=0x7ffc2242e308) at
../csu/libc-start.c:291
#17 0x00400749 in _start ()
Detaching from program: /usr/bin/kwin_x11, process 10843

Hopefully it helps.

But now i noticed something else, when i ran gdb attached to kwin process the
cpu usage from both X and kwin goes down right away, but as soon as i quit it
it goes up again. Both spike well above  50% cpu usage on a FX832 up to 90% for
X and stay there until i killed qbittorrent.

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

[Martin Gräßlin via KDE Bugzilla]

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.

[Tony via KDE Bugzilla]

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 desktop locks.
Tried to cancel the command ctrl+c, no go, i killed x to regain control

I tried again with compositor off, .It works but  while gdb is running i can't
click on anything, i mean i can, but there is no response, can't drag windows,
right click menus etc.  so cannot switch to it.

Tried to open it from the terminal and i got this error:
"Could not resolve property : linearGradient4566"

I ran "bt" before closing gdb, this is what i got:

Attaching to process 3820
[New LWP 3825]
[New LWP 3827]
[New LWP 3854]
[New LWP 3915]
[New LWP 6011]
[New LWP 6012]
[New LWP 6013]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
0x7f5378455e8d in poll () at ../sysdeps/unix/syscall-template.S:84
84  ../sysdeps/unix/syscall-template.S: No such file or directory.
(gdb) bt
#0  0x7f5378455e8d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f5376328614 in poll (__timeout=, __nfds=5,
__fds=0x1906118)
at /usr/include/x86_64-linux-gnu/bits/poll2.h:46
#2  qt_ppoll (timeout_ts=, nfds=5, fds=0x1906118) at
kernel/qcore_unix.cpp:93
#3  qt_safe_poll (fds=0x1906118, nfds=nfds@entry=5,
timeout_ts=timeout_ts@entry=0x7ffee2132320)
at kernel/qcore_unix.cpp:121
#4  0x7f5376329fb8 in QEventDispatcherUNIX::processEvents (this=, flags=..., 
flags@entry=...) at kernel/qeventdispatcher_unix.cpp:495
#5  0x7f536255e87d in QUnixEventDispatcherQPA::processEvents
(this=, flags=...)
at eventdispatchers/qunixeventdispatcher.cpp:68
#6  0x7f53762d7d9a in QEventLoop::exec (this=this@entry=0x7ffee2132460,
flags=..., 
flags@entry=...) at kernel/qeventloop.cpp:210
#7  0x7f53762e03ac in QCoreApplication::exec () at
kernel/qcoreapplication.cpp:1261
#8  0x7f5376622dbc in QGuiApplication::exec () at
kernel/qguiapplication.cpp:1639
#9  0x7f5376bc57f5 in QApplication::exec () at kernel/qapplication.cpp:2975
#10 0x7f5378734206 in kdemain (argc=1, argv=0x7ffee21326f8) at
/workspace/build/main_x11.cpp:466
#11 0x7f537837b830 in __libc_start_main (main=0x400710 ,
argc=1, 
argv=0x7ffee21326f8, init=, fini=,
rtld_fini=, 
stack_end=0x7ffee21326e8) at ../csu/libc-start.c:291
#12 0x00400749 in _start ()
(gdb) quit
A debugging session is active.

Inferior 1 [process 3820] will be detached.

Quit anyway? (y or n) y
Detaching from program: /usr/bin/kwin_x11, process 3820


At this point i gave up installed ktorrent, not a single issue, so this is on
qbitorrent if you ask me.

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

[Thomas Lübking via KDE Bugzilla]

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 whatever process else boils up in top.

And use transmission ;-)

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

[Martin Gräßlin via KDE Bugzilla]

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 kwin_x11
2. gdb --pid=
3. t a a bt

-- 
You are receiving this mail because:
You are watching all bug changes.