https://bugs.kde.org/show_bug.cgi?id=488713
--- Comment #45 from Dennis Marttinen <twe...@welho.tech> --- Reproduced as well with automatic time sync off, another kwin_wayland crash after 18:13:22 up 3 days, 20:46, 1 user, load average: 1,16, 4,38, 4,92 This is all I managed to capture from the crash this time around: Core was generated by `/usr/bin/kwin_wayland --wayland-fd 7 --socket wayland-0 --xwayland-fd 8 --xwayl'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x000075c5f8396d81 in ?? () [Current thread is 1 (LWP 1685)] Cannot QML trace cores :( [Current thread is 1 (LWP 1685)] Thread 36 (LWP 38306): Backtrace stopped: Cannot access memory at address 0x75b980bff9e0 Thread 35 (LWP 38304): Backtrace stopped: Cannot access memory at address 0x75b981fff890 Thread 34 (LWP 1765): Backtrace stopped: Cannot access memory at address 0x75c5c7dff8c0 Thread 33 (LWP 1747): Backtrace stopped: Cannot access memory at address 0x75c5d4bff8c0 ... (lots more lines like the above) dmesg shows the following: [87583.322771] kwin_wayland[1685]: segfault at 5f ip 000075c5f8396d81 sp 00007ffc94e888c0 error 4 in libQt6Core.so.6.7.2[196d81,75c5f82b1000+406000] likely on CPU 6 (core 2, socket 0) [87583.322782] Code: 31 ff 48 8d 75 b0 c6 45 af 00 48 89 5d b0 4c 89 65 b8 48 89 45 c0 e8 ce 17 f3 ff 84 c0 75 6d 48 8b 43 08 48 8d 0d 3f ff ff ff <4c> 8b 78 58 4d 89 fe 41 8b 57 08 49 8b 7d 00 8d 42 01 41 89 47 08 -- You are receiving this mail because: You are watching all bug changes.
