Bug 514912

Summary: kwin_wayland crashes when many Brave browers tabs and applications are open/used
Product: [Plasma] kwin Reporter: Nicholas Riegel <nicholasr>
Component: wayland-genericAssignee: KWin default assignee <kwin-bugs-null>
Status: NEEDSINFO BACKTRACE    
Severity: crash CC: kde
Priority: NOR    
Version First Reported In: 6.5.5   
Target Milestone: ---   
Platform: Arch Linux   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Nicholas Riegel 2026-01-21 18:50:28 UTC 
SUMMARY
kwin_wayland crashes when many Brave browers tabs and applications are open/used.  Dolphin, Konsole, Signal Messenger, Kate, Spectacle running too.   CPU and RAM usage does not seem to be an issue based on load average and PSI information history  from HTOP viewed within 20 seconds of a crash. The crash has occured 3 times today. The Arch distribution is Garuda, it was updated before the 2nd and 3rd crash. The system was rebooted between the 2nd and 3rd crash

STEPS TO REPRODUCE
1. Open 20+ Brave Browser tabs with various web applications / pages
2.  Use Brave browser and other applications
3.  All chrashes have occured when using Brave Browser

OBSERVED RESULT
Kwin crashes. The entire KDE session reloads. Konsole, Dolphn, Kate reappear. Brave Browser and Signal Messenger do not

Kernal log:
segfault at fa ip 00007f26a65bcdef sp 00007ffde6ef25e0 error 4 in libQt6Core.so.6.10.1[1bcdef,7f26a6491000+3e7000] likely on CPU 5 (core 5, socket 0)

EXPECTED RESULT
No crashes


SOFTWARE/OS VERSIONS

Linux/KDE Plasma: Garuda Linux (Arch rolling - up to date)
KDE Plasma Version: 6.5.5
KDE Frameworks Version: 6.22.0
Qt Version: 6.10.1

ADDITIONAL INFORMATION
Comment 1 David Redondo 2026-01-22 13:06:22 UTC 
Thank you for the bug report! Unfortunately I can't reproduce the crash myself on current git master, and the backtrace is incomplete and missing debug symbols for the following lines that we need to figure out exactly what's going wrong:
Could you please install debug symbols and attach a new symbolicated backtrace generated by using coredumpctl gdb in a terminal window? See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl for details about how to do this.
Thanks again!