Bug 497885

Summary:	Continuos crashing while streaming games with OBS and Discord open
Product:	[Plasma] plasmashell	Reporter:	yuurieru
Component:	generic-crash	Assignee:	Plasma Bugs List <plasma-bugs-null>
Status:	RESOLVED DUPLICATE
Severity:	crash	CC:	cwo.kde
Priority:	NOR	Keywords:	drkonqi
Version First Reported In:	6.2.4
Target Milestone:	1.0
Platform:	Arch Linux
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:
Attachments:	New crash information added by DrKonqi

Description yuurieru 2024-12-25 15:24:20 UTC

Application: plasmashell (6.2.4)

ApplicationNotResponding [ANR]: false
Qt Version: 6.8.1
Frameworks Version: 6.9.0
Operating System: Linux 6.12.6-arch1-1 x86_64
Windowing System: Wayland
Distribution: Arch Linux
DrKonqi: 6.2.4 [CoredumpBackend]

-- Information about the crash:
At first i thought it was an issue with Fedora KDE but switched to Arch and it still happens when Im playing any game while streaming and Discord is open, eventually both monitors freeze and then after about 2-3 minutes, they start allowing me to do things again but OBS, and whichever game i was playing from steam would be closed. Discord stays open and i can still hear the voice chat.

The crash can be reproduced sometimes.

-- Backtrace (Reduced):
#5  __pthread_kill_implementation (threadid=<optimized out>, signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44
#6  0x00007ad7abaa5463 in __pthread_kill_internal (threadid=<optimized out>, signo=6) at pthread_kill.c:78
#7  0x00007ad7aba4c120 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26
#8  0x00007ad7aba334c3 in __GI_abort () at abort.c:79
#9  0x00007ad79d7e3163 in amdgpu_ctx_set_sw_reset_status () at ../mesa-24.3.2/src/gallium/winsys/amdgpu/drm/amdgpu_cs.cpp:459


Reported using DrKonqi

Comment 1 yuurieru 2024-12-25 15:24:22 UTC

Created attachment 176874 [details]
New crash information added by DrKonqi

DrKonqi auto-attaching complete backtrace.

Comment 2 cwo 2024-12-26 14:11:33 UTC

Thank you for the bug report! This issue has already been filed and was determined to be an upstream issue.

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