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

            Bug ID: 492506
           Summary: kwin_wayland freezes, consumes 100% CPU, accepts no
                    input
    Classification: Plasma
           Product: kwin
           Version: master
          Platform: Other
                OS: Linux
            Status: REPORTED
          Severity: major
          Priority: NOR
         Component: core
          Assignee: kwin-bugs-n...@kde.org
          Reporter: o...@geek.co.il
  Target Milestone: ---

Created attachment 173208
  --> https://bugs.kde.org/attachment.cgi?id=173208&action=edit
coredump backtrace 1

SUMMARY
>From time to time I get a case where kwin_wayland completely freezes: no screen
updates (I can tell because I often have something running with progress
reports, such as a script in the console or a download), no mouse movement, no
keyboard input - not even VT switching.

If I SSH into the machine, I can see that kwin_wayland takes 100% CPU. From
monitoring using perf and forced core dumps, it seems to be spending the time
in harfbuzzNG under the QTextEngine::shapeTextWithHarfbuzzNG method.

STEPS TO REPRODUCE
I actually have no clue - it often happens when I'm doing something
window-management intensive (lately its been when using Android Studio with
multiple windows) but there's no specific use case.

OBSERVED RESULT
The entire computer appears to be frozen.

EXPECTED RESULT
?

SOFTWARE/OS VERSIONS
Operating System: KDE neon Unstable Edition
KDE Plasma Version: 6.1.80
KDE Frameworks Version: 6.6.0
Qt Version: 6.7.2
Kernel Version: 6.8.0-41-generic (64-bit)
Graphics Platform: Wayland
Processors: 20 × 12th Gen Intel® Core™ i7-12700H
Memory: 31.0 GiB of RAM
Graphics Processor: Mesa Intel® Graphics

ADDITIONAL INFORMATION
This has been happening since Plasma 6.0 but I'm now running 6.2 prerelease and
still happens.

When sending SIGQUIT, I get a coredump that I can get a trace from. I also
tried attaching to the running process with gdb to get stack traces, running
perf, and looking at plasma-kwin_wayland.service logs (which was fruitless
actually).

I'm going to add some attachment with data that I hope will be useful.

I often recover by killing kwin_wayland, which resets the session - keeping KDE
apps and killing everything else, but its better than nothing (yay for wayland
compositor handover!).

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

Reply via email to