SUMMARY With many overlayfs mounts present, eg when created by microk8s, several KDE applications and Plasmashell consume 100% CPU, spam notifications and become unresponsive. Possibly related to bug 413110 STEPS TO REPRODUCE 1. Install microk8s: sudo snap install --classic microk8s 2. Run many containers: sudo microk8s.kubectl run nginx --image=nginx --replicas=50 --expose=true --port='80' 3. Tear down: sudo microk8s.kubectl delete service/nginx deployment/nginx ; sudo snap remove --purge microk8s This is likely reproducible by running a bunch of containers in regular Docker, too. OBSERVED RESULT * Kate, Gwenview, Dolphin consume 100% CPU and become partially unresponsive with significant delay responding to inputs * Dolphin begins consuming multiple gigabytes of RAM - Heaptrack suggests most of this goes via Solid::StorageAccess::accessibilityChanged * Plasmashell consumes 100% CPU and spams "Filesystem is not responding" notifications * If the notification backlog is not cleared fast enough, Plasmashell crashes EXPECTED RESULT None of the above should occur SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 19.10 + kubuntu backports PPA (available in About System) KDE Plasma Version: 5.17.5 KDE Frameworks Version: 5.66.0 Qt Version: 5.12.4
Has anybody found any workaround? Is it possible to tell plasmashell/dolphin/gwenview to ignore certain mount points?
Hello and thank you again for the bug report! Unfortunately we were not able to address it yet, nor even manage to reproduce the issue ourselves. Can we ask you to please check if this issue is still happening with Plasma 5.27? If it is, please change the status to REPORTED. Thanks a lot!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!