| Summary: | Last update from KDE destroyed system performance and loop CPU & GPU load | ||
|---|---|---|---|
| Product: | [Plasma] kwin | Reporter: | Roman <phoenix91140> |
| Component: | core | Assignee: | KWin default assignee <kwin-bugs-null> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | CC: | kde, nate, nicolas.fella, qydwhotmail |
| Priority: | NOR | ||
| Version First Reported In: | 5.27.7 | ||
| Target Milestone: | --- | ||
| Platform: | openSUSE | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: | cpu load | ||
Can you reproduce the issue when Telegram is *not* running? (In reply to Nate Graham from comment #1) > Can you reproduce the issue when Telegram is *not* running? Yes. Any windows a bit moving around or even opened Ksysguard alone and cpu load goes too high compared to older versions of KDE Thanks. Please attach perf top report, otherwise there is no way to know what was wrong. Performance is something constantly improved on and there is nothing in this report that aids in that. 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! This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now 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 Thank you for helping us make KDE software even better for everyone! |
Created attachment 161529 [details] cpu load SUMMARY Lastest update (5.27.7) loads CPU for 33-44% all the time. Top processes that eat whole cpu are KWin_X11 (if Wayland, then Kwin_Wayland) and plasma_shell. Any window movement also increases CPU load dramatically. Seems like something messed up with patches applied to KWin on latest (5.27.7) update. Unfortunately rollback to 5.27.6 impossible (due to no packaged remaining in system and OpenSUSE repository). Seems like KWin keep doing something erroneous in the loop loading half of cpu almost. All the rest in whole system is fine, expect KWin. Please fix bug. STEPS TO REPRODUCE 1. Update KDE 5.27.7 2. Start opening lightweight apps, like Telegram, Ksysguard and even move windows around and get almost 100% cpu load by Kwin_X11 and plasmashell 3. OBSERVED RESULT KWin does something incorrect with rendering utilizing CPU in the loop and also wasting GPU time. EXPECTED RESULT Fast, flawless almost no load operation as before update. SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.27.7 KDE Frameworks Version: 5.109.0 Qt Version: 5.15.10 OpenSUSE Tumbleweed x86_64. Intel® Xeon® CPU E3-1575M v5 @ 3.00GHz, Quadro P3000/PCIe/SSE2. ADDITIONAL INFORMATION