Bug 449776 - Plasmashell process used 100% CPU, and then got killed by OOM
Summary: Plasmashell process used 100% CPU, and then got killed by OOM
Status: RESOLVED WAITINGFORINFO
Alias: None
Product: plasmashell
Classification: Plasma
Component: generic-performance (show other bugs)
Version: master
Platform: Other Linux
: NOR normal
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-02-08 10:48 UTC by ratijas
Modified: 2022-02-23 23:49 UTC (History)
2 users (show)

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

Attachments
Plasma OOM kernel logs (17.93 KB, text/plain)
2022-02-08 10:48 UTC, ratijas 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description ratijas 2022-02-08 10:48:42 UTC 
Created attachment 146426 [details]
Plasma OOM kernel logs

SUMMARY

I was working in text editor as usual, nothing special. But suddenly and unexpectedly I heard fans spinning like crazy, checked out htop — and there was plasmashell on the top row eating exactly 100% CPU. Few moments later it disappeared and the desktop went black. I checked out coredumpctl, but there were no new entries. Then I checked kernel logs (dmesg), and found a lot of messages from OOM (out of memory) guard.

STEPS TO REPRODUCE
1. ???
2. …
3. ¡Ba-da-boom!

OBSERVED RESULT
All hell breaks loose, and drags Plasma into the abyss.

EXPECTED RESULT
Welp, …

SOFTWARE/OS VERSIONS
Operating System: Arch Linux
KDE Plasma Version: 5.24.80
KDE Frameworks Version: 5.91.0
Qt Version: 5.15.2
Kernel Version: 5.16.5-arch1-1 (64-bit)
Graphics Platform: X11
Processors: 8 × Intel® Core™ i7-6700HQ CPU @ 2.60GHz
Memory: 15.6 GiB of RAM
Graphics Processor: NVIDIA GeForce GTX 970M/PCIe/SSE2

plasma-desktop: 963b4ee7a1c56ee68a2d5bf0557862d497fea974
plasma-workspace: 94fc46e38bbdbb3e75aba4a4547d667b3b59af39
plasma-framework: 850051e0a0b577e6c22b67e2ba04a7c8c8ed25cb
Comment 1 David Edmundson 2022-02-23 23:49:12 UTC 
There is not enough there to be able to investigate. Sorry.
Hopefully a future update will address there.