Bug 512403 - kwin_wayland SIGSEGV in QObjectPrivate::deleteChildren (Qt6) randomly when closing windows
Summary: kwin_wayland SIGSEGV in QObjectPrivate::deleteChildren (Qt6) randomly when cl...
Status: RESOLVED DUPLICATE of bug 511948
Alias: None
Product: kwin
Classification: Plasma
Component: wayland-generic (other bugs)
Version First Reported In: 6.5.3
Platform: Arch Linux Linux
: NOR crash
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-11-20 19:25 UTC by Higor Silva
Modified: 2025-11-20 22:11 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments
logs captured with coredumpctl (45.57 KB, text/plain)
2025-11-20 19:25 UTC, Higor Silva
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Higor Silva 2025-11-20 19:25:30 UTC
Created attachment 187005 [details]
logs captured with coredumpctl

SUMMARY

I am experiencing random kwin_wayland crashes (Signal 11) specifically when closing windows. It does not happen every time; it appears to be random (I can go days or even weeks without issues), but the trigger is always the action of closing an application window.

I captured a coredump, and the stack trace points towards an issue with Qt6 object destruction (QObjectPrivate::deleteChildren and QQuickItem).

STEPS TO REPRODUCE

1. Login to a Plasma (Wayland) session.
2. Open application windows normally.
3. Close a window.

OBSERVED RESULT
The compositor (kwin_wayland) crashes with a Segmentation Fault (Signal 11), terminating the session immediately

EXPECTED RESULT
The window should close normally without crashing the compositor.

SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 6.5.3
KDE Frameworks Version: 6.20.0
Qt Version: 6.10.0
Kernel Version: 6.17.8-zen1-1-zen (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i5-1035G1 CPU @ 1.00GHz
Memory: 16 GiB of RAM (15.2 GiB usable)
Graphics Processor: Intel® UHD Graphics
Manufacturer: HP
Product Name: HP 240 G7 Notebook PC

ADDITIONAL INFORMATION

I initially suspected a custom window decoration (Aurorae) or a hardware issue (RAM), but I reverted my system to the stock Breeze theme and removed third-party widgets. The crash persists with the exact same stack trace on a standard configuration.
Comment 1 TraceyC 2025-11-20 21:34:30 UTC
Searchable backtrace

Stack trace of thread 1401:
#0  0x00007fd82229890c n/a (libc.so.6 + 0x9890c)
#1  0x00007fd82223e3a0 raise (libc.so.6 + 0x3e3a0)
#2  0x00007fd825c4ee57 _ZN6KCrash19defaultCrashHandlerEi (libKF6Crash.so.6 + 0x7e57)
#3  0x00007fd82223e4d0 n/a (libc.so.6 + 0x3e4d0)
#4  0x00007fd822bbc6ef _ZN14QObjectPrivate14deleteChildrenEv (libQt6Core.so.6 + 0x1bc6ef)
#5  0x00007fd822bc339e _ZN7QObjectD2Ev (libQt6Core.so.6 + 0x1c339e)
#6  0x00007fd824b72092 _ZN10QQuickItemD1Ev (libQt6Quick.so.6 + 0x172092)
#7  0x00007fd7e84c8502 n/a (libcorebindingsplugin.so + 0xc502)
#8  0x00007fd822bbc6e2 _ZN14QObjectPrivate14deleteChildrenEv (libQt6Core.so.6 + 0x1bc6e2)
#9  0x00007fd822bc339e _ZN7QObjectD2Ev (libQt6Core.so.6 + 0x1c339e)
#10 0x00007fd824e3aa12 n/a (libQt6Quick.so.6 + 0x43aa12)
#11 0x00007fd822bbc6e2 _ZN14QObjectPrivate14deleteChildrenEv (libQt6Core.so.6 + 0x1bc6e2)
#12 0x00007fd822bc339e _ZN7QObjectD2Ev (libQt6Core.so.6 + 0x1c339e)
#13 0x00007fd824e39426 n/a (libQt6Quick.so.6 + 0x439426)
#14 0x00007fd822bbc6e2 _ZN14QObjectPrivate14deleteChildrenEv (libQt6Core.so.6 + 0x1bc6e2)
#15 0x00007fd822bc339e _ZN7QObjectD2Ev (libQt6Core.so.6 + 0x1c339e)
#16 0x00007fd824e3aa12 n/a (libQt6Quick.so.6 + 0x43aa12)
#17 0x00007fd822bbc6e2 _ZN14QObjectPrivate14deleteChildrenEv (libQt6Core.so.6 + 0x1bc6e2)
#18 0x00007fd822bc339e _ZN7QObjectD2Ev (libQt6Core.so.6 + 0x1c339e)
#19 0x00007fd824e3aa12 n/a (libQt6Quick.so.6 + 0x43aa12)
#20 0x00007fd7f4c6ffb9 n/a (org.kde.kwin.aurorae.so + 0x10fb9)
#21 0x00007fd7f4c70235 n/a (org.kde.kwin.aurorae.so + 0x11235)
#22 0x00007fd8255764ca n/a (libkwin.so.6 + 0x1764ca)
#23 0x00007fd8257ef62a _ZN4KWin6WindowD2Ev (libkwin.so.6 + 0x3ef62a)
#24 0x00007fd825833ce5 n/a (libkwin.so.6 + 0x433ce5)
#25 0x00007fd825606b0e _ZN4KWin15AnimationEffect15postPaintScreenEv (libkwin.so.6 + 0x206b0e)
#26 0x00007fd82560b98c _ZN4KWin14EffectsHandler15postPaintScreenEv (libkwin.so.6 + 0x20b98c)
#27 0x00007fd82560b98c _ZN4KWin14EffectsHandler15postPaintScreenEv (libkwin.so.6 + 0x20b98c)
#28 0x00007fd82575544a _ZN4KWin14WorkspaceScene9postPaintEv (libkwin.so.6 + 0x35544a)
#29 0x00007fd82558e459 _ZN4KWin10Compositor9compositeEPNS_10RenderLoopE (libkwin.so.6 + 0x18e459)
#30 0x00007fd822bd716f n/a (libQt6Core.so.6 + 0x1d716f)
#31 0x00007fd8255b490b _ZN4KWin10RenderLoop14frameRequestedEPS0_ (libkwin.so.6 + 0x1b490b)
#32 0x00007fd822bc44f6 _ZN7QObject5eventEP6QEvent (libQt6Core.so.6 + 0x1c44f6)
#33 0x00007fd823d020a0 _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt6Widgets.so.6 + 0x1020a0)
#34 0x00007fd822b6a6c8 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt6Core.so.6 + 0x16a6c8)
#35 0x00007fd822d2c6af _ZN14QTimerInfoList14activateTimersEv (libQt6Core.so.6 + 0x32c6af)
#36 0x00007fd822d2f901 _ZN20QEventDispatcherUNIX13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt6Core.so.6 + 0x32f901)
#37 0x00007fd823934773 _ZN23QUnixEventDispatcherQPA13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt6Gui.so.6 + 0x734773)
#38 0x00007fd822b75a86 _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt6Core.so.6 + 0x175a86)
#39 0x00007fd822b6f171 _ZN16QCoreApplication4execEv (libQt6Core.so.6 + 0x16f171)
#40 0x000055b044329ab4 n/a (/usr/bin/kwin_wayland + 0x3cab4)
#41 0x00007fd822227635 n/a (libc.so.6 + 0x27635)
#42 0x00007fd8222276e9 __libc_start_main (libc.so.6 + 0x276e9)
#43 0x000055b04432ff75 n/a (/usr/bin/kwin_wayland + 0x42f75)
Comment 2 TraceyC 2025-11-20 22:11:40 UTC
Thanks for the crash report.

The backtrace looks very similar to, but not identical to bug 511948. It looks like the difference is just due to Breeze vs Aurorae. I'm going to merge this in with the older report. Thanks.

*** This bug has been marked as a duplicate of bug 511948 ***