Summary: | Uses 100% CPU | ||
---|---|---|---|
Product: | [Plasma] kwin | Reporter: | Nicolas Girard <girard.nicolas> |
Component: | general | Assignee: | KWin default assignee <kwin-bugs-null> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | CC: | ennereu |
Priority: | NOR | ||
Version: | 5.16.3 | ||
Target Milestone: | --- | ||
Platform: | Other | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Nicolas Girard
2019-07-29 09:04:22 UTC
Things went back to normal after pkill -9 kwin ; kwin& I regularly need to do so, although I'm unsure how to reproduce this defect. Seems to be related to https://bugs.kde.org/show_bug.cgi?id=364709 but that got actually fixed in 5.15. Did you activate Desktop Grid? Thanks for your feedback. > Did you activate Desktop Grid? Yes, I did > Seems to be related to https://bugs.kde.org/show_bug.cgi?id=364709 but that got actually fixed in 5.15. All I can tell, is that my packages earlier than 5.15. I've switched to the "compact" (effect ? Dunno how these are called), to see how it goes. 1. Which version version do you use if not 5.16.3 and I suggest updating your packages. 2. Tell wether deactivating "Desktop Grid" helps > 1. Which version version do you use if not 5.16.3 and I suggest updating your packages. I confirm I'm using version 5.16.3. I meant "more recent", not "earlier", sorry. > 2. Tell whether deactivating "Desktop Grid" helps What I can do is keep using my machine using the "compact" effect for a few days, and report back afterwards. Please provide the following info: - steps to reproduce - backtrace when kwin consumes 100% cpu https://community.kde.org/KWin/Debugging 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! |