Bug 510600

Summary:	plasmashell becomes randomly unresponsive and takes up 100% of CPU until killed
Product:	[Plasma] plasmashell	Reporter:	misterx42
Component:	generic-crash	Assignee:	Plasma Bugs List <plasma-bugs-null>
Status:	RESOLVED WORKSFORME
Severity:	normal	CC:	kde, nate
Priority:	NOR
Version First Reported In:	6.4.5
Target Milestone:	1.0
Platform:	Other
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:
Attachments:	gdb dump

Description misterx42 2025-10-14 14:09:19 UTC

SUMMARY
plasmashell's process (/usr/bin/plasmahell --no-respawn) recently started randomly becoming completely unresponsive, taking up 100% CPU (as per htop), clogging up the system use in general, and never becoming responsive again until killed. There's no pattern to this, and I can't find any crashes or error messages related to this on my system.

STEPS TO REPRODUCE
1. Use the system as normal
2. Task bar stops working
3. CPU usage then spikes to max and the process goes completely unresponsive

OBSERVED RESULT
See above

EXPECTED RESULT
Not crash

SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 6.4.5
KDE Frameworks Version: 6.19.0
Qt Version: 6.10.0
Kernel Version: 6.17.1-arch1-1 (64-bit)
Graphics Platform: Wayland
Processors: 12 × AMD Ryzen 5 1600 Six-Core Processor
Memory: 8 GiB of RAM (7.7 GiB usable)
Graphics Processor: AMD Radeon RX 6700

Comment 1 David Edmundson 2025-10-14 14:39:06 UTC

Unfortunately we need some more information to diagnose this.

If you can run the following:

sudo gdb --pid `pidof plasmashell`

then when it attaches run:

thread apply all bt


and paste the result

Comment 2 misterx42 2025-10-15 18:20:13 UTC

Created attachment 185815 [details]
gdb dump

Comment 3 misterx42 2025-10-15 18:21:23 UTC

Hopefully I've done it correctly. As luck would have it, it just went unresponsive right before I created the dump, so hopefully this helps. Worth nothing that this time the CPU usage didn't spike, plasmashell just stopped responding to anything except for the already opened terminal emulator.

Comment 4 Bug Janitor Service 2025-10-30 03:47:47 UTC

🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME.

For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging.

Thank you for helping us make KDE software even better for everyone!

Comment 5 Nate Graham 2025-12-10 18:15:57 UTC

Not really any help, unfortunately. It doesn't show anything going wrong, and the trace is missing all debug symbols, too.

Unfortunately this bugzilla ticket is more of an un-actionable observation right now, and not an actionable, reproducible bug report. I'll have to close it. Please do let us know if you manage to identify a pattern or a set of discrete steps to reproduce!