SUMMARY There appears to be a memory leak in the kioworker process that causes increasing memory usage over time without it being released, impacting system performance until targeted by OOM Killer and terminated STEPS TO REPRODUCE Use Dolphin to perform file system operations, specifically accessing SMB shares and performing searches for specific files. Monitor the memory usage of the kioworker process using a system monitor tool like htop or top. Observe the increasing memory consumption by kioworker that is not released even after tasks are completed. OBSERVED RESULT The kioworker process steadily consumes more memory over time without releasing it, leading to a noticeable memory leak. EXPECTED RESULT The kioworker process should release memory after completing its task, maintaining stable memory usage without excessive growth. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Garuda Linux KDE Plasma Version: plasmashell 6.3.2 KDE Frameworks Version: 6.11.0 Qt Version: 6.8.2 ADDITIONAL INFORMATION The issue is primarily observed during regular file operations in Dolphin while accessing networked shares via SMB. Memory leak is not immediately apparent but becomes noticeable after extended usage. The process does not seem to release memory after completing tasks like file transfers or searches. ─λ journalctl -xe | grep -i "killed process" Mar 23 04:45:19 kernel: Out of memory: Killed process 4010253 (kioworker) total-vm:102261920kB, anon-rss:45431184kB, file-rss:2232kB, shmem-rss:0kB, UID:1000 pgtables:199964kB oom_score_adj:200 sudo netstat -tunp | grep kioworker tcp 0 0 192.168.20.75:32968 192.168.20.26:445 ESTABLISHED 139478/kioworker tcp 0 232 192.168.20.75:32972 192.168.20.26:445 ESTABLISHED 139480/kioworker tcp 0 0 192.168.20.75:32926 192.168.20.26:445 ESTABLISHED 139458/kioworker tcp 0 0 192.168.20.75:32954 192.168.20.26:445 ESTABLISHED 139482/kioworker tcp 0 0 192.168.20.75:32938 192.168.20.26:445 ESTABLISHED 139439/kioworker tcp 0 109 192.168.20.75:32982 192.168.20.26:445 ESTABLISHED 139476/kioworker
Created attachment 179648 [details] Dolphin left Idle. Attempted to replicate to get additional evidence of issue. Performed a search for Xenia.log on SMB share. Came back later and memory usage was high, afterwards terminated dolphin and memory was released.
Your system is quite out of date, missing Plasma 6.3.3 and Frameworks 6.12. Please update and see if the bug is still present.
Created attachment 179741 [details] Replication after update Have updated as requested to Plasma 6.3.3 and Frameworks 6.12 and re-tested. Issue was replicated.
(In reply to Leona from comment #3) > Created attachment 179741 [details] > Replication after update > > Have updated as requested to Plasma 6.3.3 and Frameworks 6.12 and re-tested. > Issue was replicated. I'll try to reproduce this on a clean Garuda and Arch installation when I get the chance. To clarify, I should set up a Samba share with a decently sized directory tree and browse around and do different searches without closing Dolphin to cause the leak?