Created attachment 152271 [details] kwin_x11 and xorg log SUMMARY The fps will drop to 30 in 2-4hours, and drop to 20fps in 4 - 8hours, and will keep decline. In this situaltion, Xorg will take about 50% cpu even close all windows(cpu consume will drop a little bit, but it will back to 50% if there are any action performed), and will take more with the time passing. eg: It will take about 100% when fps go down to 15-20. kwin_x11 consume up to 20% cpu according the number of windows. Also tested glxgears, and it shows good performance with 60 fps. Tried restart plasmashell with "--replace" option, not work. The only solution i found is to restart kwin_11 with "--replace" options. But it will keep happened in next 2hours. There are no related error log print by Xorg or Kwin_x11, i will attach logs below. STEPS TO REPRODUCE 1. Login to system 2. Normal use 3. FPS drop SOFTWARE/OS VERSIONS KDE Plasma Version: 5.25.5 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.6 Kernel Version: 5.19.9-arch1-1 (64-bit) Graphics Platform: X11 Processors: 6 × Intel® Core™ i5-9500T CPU @ 2.20GHz Memory: 62.6 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 630 ADDITIONAL INFORMATION
A lot of messages like this: [ 20012.277] (EE) event9 - SONiX USB DEVICE: client bug: event processing lagging behind by 28ms, your system is too slow [ 20320.057] (EE) event9 - SONiX USB DEVICE: client bug: event processing lagging behind by 24ms, your system is too slow [ 20816.976] (EE) event15 - Logitech MX Master 3: client bug: event processing lagging behind by 33ms, your system is too slow [ 20816.976] (EE) client bug: timer event15 debounce short: scheduled expiry is in the past (-21ms), your system is too slow [ 20921.164] (EE) event15 - Logitech MX Master 3: client bug: event processing lagging behind by 22ms, your system is too slow [ 20921.978] (EE) event15 - Logitech MX Master 3: client bug: event processing lagging behind by 29ms, your system is too slow [ 22127.914] (EE) event15 - Logitech MX Master 3: client bug: event processing lagging behind by 32ms, your system is too slow
Yeah, i do notice that too, but it's seems the result that compositor lagged[1]. And it may noe caused this problem i think, since there are actually a number of ubuntu and debian users reported it to upstream[2][3][4]. I also found multiple bugs in bugs.kde.org which mentioned this[5], but seems none of it is related to "compositor lagged continuous". Since there are no more detail logs in Xorg and kde, we think we may try to find a way to figured the root case which caused it. May be more verbose log or flame graph through efbp(with SystemTap or perf)? I am not familiar with kde an Xorg, so i have no idea how to apporach it. I am still trying to isolate this case, and see if I can find out more detail about this. [1]https://askubuntu.com/questions/1292691/why-am-i-getting-event-processing-lagging-behind-msg-in-ubuntu-20-10/1292837#1292837 [2]https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-libinput/+bug/1914806 [3]https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968093 [4]https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1870597 [5]https://bugs.kde.org/show_bug.cgi?format=multiple&id=454590 (In reply to Nate Graham from comment #1) > A lot of messages like this: > > [ 20012.277] (EE) event9 - SONiX USB DEVICE: client bug: event processing > lagging behind by 28ms, your system is too slow > [ 20320.057] (EE) event9 - SONiX USB DEVICE: client bug: event processing > lagging behind by 24ms, your system is too slow > [ 20816.976] (EE) event15 - Logitech MX Master 3: client bug: event > processing lagging behind by 33ms, your system is too slow > [ 20816.976] (EE) client bug: timer event15 debounce short: scheduled expiry > is in the past (-21ms), your system is too slow > [ 20921.164] (EE) event15 - Logitech MX Master 3: client bug: event > processing lagging behind by 22ms, your system is too slow > [ 20921.978] (EE) event15 - Logitech MX Master 3: client bug: event > processing lagging behind by 29ms, your system is too slow > [ 22127.914] (EE) event15 - Logitech MX Master 3: client bug: event > processing lagging behind by 32ms, your system is too slow
Does this still happen in Plasma 6?
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
Hi, I have migrated to KDE plasma Wayland session for a while, but fortunately, I haven't reinstalled my system yet. I'll check if I can reproduce this issue by switching back to X11 session, possibly this weekend.
Hi, I am running KDE plasma 6 for a few days, and unable to reproduce this issues now, although Kwin_x11 and plasma-shell stop responding everyday. Consider I migrated to Wayland for a long time, and KDE plasma performs well, I am going to change this issue to WORKSFORME. Thanks for everyone. PS: I am wondering if it's necessary to report the not responding problem mentioned before, will try to search it online to see if I can got more information.
🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME. For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging. Thank you for helping us make KDE software even better for everyone!
🐛🧹 This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME.