Bug 462143 - kwin crashing often on amd
Summary: kwin crashing often on amd
Status: RESOLVED DUPLICATE of bug 461316
Alias: None
Product: kwin
Classification: Plasma
Component: platform-x11-standalone (show other bugs)
Version: 5.26.3
Platform: Other Linux
: NOR crash
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-11-22 23:17 UTC by CapsAdmin
Modified: 2023-01-19 19:51 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
I had DISPLAY=:0 kwin --replace running in another virtual console session and dumped the output of the terminal. (63.28 KB, text/plain)
2022-11-22 23:17 UTC, CapsAdmin
Details

Note You need to log in before you can comment on or make changes to this bug.
Description CapsAdmin 2022-11-22 23:17:05 UTC
Created attachment 153953 [details]
I had DISPLAY=:0 kwin --replace running in another virtual console session and dumped the output of the terminal.

SUMMARY
Every now and then kwin crashes. This has been going on for a long time now. I think there was a period it didn't happen so much but I can't remember.

STEPS TO REPRODUCE
This feels GPU driver related as it tends to happen when starting an application that creates a new opengl context (like a game or application with opengl rendering) or sometimes even when doing something intensive on the GPU.

I'm not able to reliably reproduce this. Right now it happened when I started spotify and I had DISPLAY=:0 kwin --replace running in another virtual console session. 

SOFTWARE/OS VERSIONS
Linux/KDE Plasma:  KDE neon 5.26
KDE Kwin Version: 5.26.3
KDE Plasma Version: 5.26.3
KDE Frameworks Version: 5.100.0
Qt Version: 5.15.7
GPU:  Navi 21 [Radeon RX 6900 XT]
Mesa driver Version: 22.2.1

ADDITIONAL INFORMATION
I can try to attach a backtrace at some point, but I've been postponing reporting about this issue for a long time now. I figure a log from kwin is a good start.

I also started kwin now dumping its log to a file for maybe better context.
Comment 1 Zamundaaa 2022-11-23 17:42:08 UTC

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