Created attachment 185765 [details]
GDB backtrace without expanded variables

***
If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org

If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports

Please remove this comment after reading and before submitting - thanks!
***

SUMMARY


STEPS TO REPRODUCE

Unsure what triggers this, I was merely moving my mouse within a window when this happened.

OBSERVED RESULT

kwin_wayland freezes with 100% CPU usage on one core and the session cannot be interacted with, neither via keyboard nor mouse.

EXPECTED RESULT

kwin keeps working normally.

SOFTWARE/OS VERSIONS

$ kinfo
Operating System: Fedora Linux 43
KDE Plasma Version: 6.4.5
KDE Frameworks Version: 6.18.0
Qt Version: 6.9.2
Kernel Version: 6.17.1-300.fc43.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 12 × AMD Ryzen 5 PRO 4650U with Radeon Graphics
Memory: 40 GiB of RAM (38.4 GiB usable)
Graphics Processor: AMD Radeon Graphics

ADDITIONAL INFORMATION

Running

```
$ qdbus-qt6 org.kde.KWin /KWin supportInformation
```

as recommended on https://community.kde.org/KWin/Debugging just times out.

journald output for the current boot is attached. The crash at the end was caused by me sending SIGSEGV to kwin so that it generates a coredump in dr. konqi.

There are also some backtraces attached. One was generated by running

```
sudo gdb -pid $(pidof kwin_wayland) -batch -ex "set logging file kwin_wayland.gdb" -ex "set logging enabled on" -ex "continue" -ex "thread apply all backtrace" -ex "quit"
```

the other (with expanded variables) by running

```
sudo gdb -pid $(pidof kwin_wayland) -batch -ex "set logging file kwin_wayland_full.gdb" -ex "set logging enabled on" -ex "continue" -ex "thread apply all backtrace full" -ex "quit"
```