Bug 502850 - Massive number of loop devices freezes Plasma
Summary: Massive number of loop devices freezes Plasma
Status: REPORTED
Alias: None
Product: plasmashell
Classification: Plasma
Component: generic-performance (other bugs)
Version First Reported In: 6.3.4
Platform: Arch Linux Linux
: NOR normal
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-04-15 17:26 UTC by Adrian
Modified: 2025-07-05 10:46 UTC (History)
3 users (show)

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


Attachments
reproducer script (434 bytes, application/x-shellscript)
2025-04-15 17:26 UTC, Adrian
Details
top memory usage (75.84 KB, image/png)
2025-04-15 17:29 UTC, Adrian
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Adrian 2025-04-15 17:26:52 UTC
Created attachment 180294 [details]
reproducer script

SUMMARY
i have a program running which uses lots (>20k) loop devices.
after starting the program the desktop does not work anymore.
switching windows with alt-tab works like before.
but clicking the "K" button is ignored.

top shows that: (for ~10k loop devices)
kded6  uses 100% cpu and the ram usage increases sharply (>3GB)
plasmashell goes to 200% cpu and uses more ram (>5GB)

after some time (~15m) it becomes responsive again.
but big ram usage continues

i attach a reduced testcase script
it attaches loop devices and should very easily show the problem 

STEPS TO REPRODUCE
1. run the attached script or open lots of loop devices

OBSERVED RESULT
kde is not responsive any more

EXPECTED RESULT
attaching of loop devices should not disturb kde in any kind

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 6.3.4
KDE Plasma Version: 6.3.4
KDE Frameworks Version: 6.12.0
Qt Version: 6.9.0

ADDITIONAL INFORMATION
Comment 1 Adrian 2025-04-15 17:29:36 UTC
Created attachment 180295 [details]
top memory usage
Comment 2 Nate Graham 2025-04-16 16:43:45 UTC
This is very far outside of the realm of normal activity.

You may have uncovered a legitimate performance issue, but regardless, I would recommend changing the program to not do this anymore.