Bug 501100 - KWin crashes when alt+tabbing out of a Konsole window
Summary: KWin crashes when alt+tabbing out of a Konsole window
Status: RESOLVED UPSTREAM
Alias: None
Product: kwin
Classification: Plasma
Component: generic-crash (show other bugs)
Version: 6.3.2
Platform: Arch Linux Linux
: NOR crash
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-03-05 13:45 UTC by Tom
Modified: 2025-03-05 17:32 UTC (History)
1 user (show)

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

Attachments
Crash Log from Crash Handler (25.16 KB, text/vnd.kde.kcrash-report)
2025-03-05 13:45 UTC, Tom 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Tom 2025-03-05 13:45:41 UTC 
Created attachment 179144 [details]
Crash Log from Crash Handler

SUMMARY
alt+tabbing out of a Konsole window often causes Kwin crashes. 

STEPS TO REPRODUCE
1. Open any application, preferably a heavy application like an IDE or video editor, seems to happen more under load
2. Alt+Shift+T to open a Konsole window
3. Alt tab out of the window

OBSERVED RESULT
The screen freezes, turns black, then re-appears. All open apps will also crash. 

EXPECTED RESULT
Alt+tab out of the window with no crash

SOFTWARE/OS VERSIONS
KDE Plasma Version: 6.3.2
KDE Frameworks Version: 6.1.0
Qt Version: 6.8.2

HARDWARE: 
Processor: 12 × AMD Ryzen 5 3600 6-Core Processor
Memory: 15.5 GiB
GPU: AMD Radeon RX 6600 XT (Discrete)
Manufacturer: Micro-Star International Co., Ltd

ADDITIONAL INFORMATION
- This has been a long standing bug for me, going back since plasma 6.2.5
- It has appeared on both Arch and Fedora
- It has happened when alt+tabbing out of other apps, but mainly Konsole.
- I am not able reproduce the bug every time, but it happens regularly enough. 
- I am sure there is more to this bug, but this everything I know, I would appreciate some help in investigating it!
- I have attached crash logs.
Comment 1 Nate Graham 2025-03-05 17:32:52 UTC 
The backtrace is missing debug symsolb, but it's also enough to show that the issue is in the graphics drivers:

Thread 1 (Thread 0x783aa3fff6c0 (LWP 1006)):
[KCrash Handler]
#4  0x0000783ab1815a1c in ?? () from /usr/lib/libgallium-24.3.4-arch1.1.so
#5  0x0000783ab18166c0 in ?? () from /usr/lib/libgallium-24.3.4-arch1.1.so
#6  0x0000783ab187afa4 in ?? () from /usr/lib/libgallium-24.3.4-arch1.1.so
#7  0x0000783ab1815859 in ?? () from /usr/lib/libgallium-24.3.4-arch1.1.so
#8  0x0000783ab1adf7ce in ?? () from /usr/lib/libgallium-24.3.4-arch1.1.so
#9  0x0000783ab1f2a4b1 in ?? () from /usr/lib/libgallium-24.3.4-arch1.1.so
#10 0x0000783ab1f2ec0e in ?? () from /usr/lib/libgallium-24.3.4-arch1.1.so
#11 0x0000783ab1f2fe1f in ?? () from /usr/lib/libgallium-24.3.4-arch1.1.so
#12 0x0000783ab1f61f3b in ?? () from /usr/lib/libgallium-24.3.4-arch1.1.so
#13 0x0000783ab1add8a4 in ?? () from /usr/lib/libgallium-24.3.4-arch1.1.so
#14 0x0000783ab1b1271d in ?? () from /usr/lib/libgallium-24.3.4-arch1.1.so
#15 0x0000783ac18a370a in ?? () from /usr/lib/libc.so.6
#16 0x0000783ac1927aac in ?? () from /usr/lib/libc.so.6