https://bugs.kde.org/show_bug.cgi?id=517653

            Bug ID: 517653
           Summary: Plasmashell leaks File Descriptors (4 per hover) on
                    Task Manager thumbnails
    Classification: Plasma
           Product: plasmashell
      Version First 6.5.6
       Reported In:
          Platform: Ubuntu
                OS: Linux
            Status: REPORTED
          Severity: crash
          Priority: NOR
         Component: Task Manager and Icons-Only Task Manager widgets
          Assignee: [email protected]
          Reporter: [email protected]
                CC: [email protected]
  Target Milestone: 1.0

I have discovered a consistent file descriptor leak in Plasma 6. Every time a
window thumbnail preview is triggered in the Task Manager, the target
application (Chrome, Edge, etc.) gains several file descriptors that are never
released after the preview is closed.

Steps to reproduce:
Open a browser (e.g., Microsoft Edge).
Monitor FD count: watch "ls /proc/$(pidof plasmashell)/fd | wc -l"
Hover the mouse over the taskbar icon to show the thumbnail preview.
Move the mouse away to hide the preview.
Re-check FD count.

Actual Results:
The FD count increases by exactly 4 every time (e.g., from 773 to 777, then to
781).

Expected Results:
All file descriptors created for the Screencast/PipeWire stream should be
closed once the preview is hidden.


Updated to 6.5.6 and leaks still exists. Can we continue here?
Operating System: Kubuntu 25.10
KDE Plasma Version: 6.5.6
KDE Frameworks Version: 6.20.0
Qt Version: 6.9.2
Kernel Version: 6.17.0-14-generic (64-bit)
Graphics Platform: Wayland
Processors: 12 × AMD Ryzen 5 5600G with Radeon Graphics
Memory: 32 GiB of RAM (31,2 GiB usable)
Graphics Processor: NVIDIA GeForce RTX 3050
Manufacturer: Gigabyte Technology Co., Ltd.
Product Name: B450M DS3H

watch -n 1 "ls /proc/$(pidof plasmashell)/fd | wc -l"
994



for pid in $(pgrep -u $USER -x "plasmashell|kwin_wayland|msedge|chrome|brave");
do

  echo "PID $pid ($(ps -p $pid -o comm=)): $(ls /proc/$pid/fd | xargs -I {}
readlink /proc/$pid/fd/{} | grep anon_inode | wc -l)";

done
ls: cannot open directory '/proc/2310/fd': Permission denied
PID 2310 (kwin_wayland): 0
PID 2428 (plasmashell): 912
PID 212798 (msedge): 43
PID 212813 (msedge): 0
PID 212814 (msedge): 0
PID 212816 (msedge): 0
PID 212854 (msedge): 24
PID 212856 (msedge): 7
PID 212870 (msedge): 6
PID 212886 (msedge): 8
PID 212908 (msedge): 8
PID 212941 (msedge): 2
PID 212942 (msedge): 11
PID 212977 (msedge): 11
PID 213010 (msedge): 8
PID 213145 (msedge): 8
PID 213168 (msedge): 6
PID 213239 (msedge): 8
PID 213280 (msedge): 8
PID 213340 (msedge): 8
PID 213490 (msedge): 8
PID 213546 (msedge): 8
PID 213596 (msedge): 8
PID 213636 (msedge): 8
PID 213686 (msedge): 8
PID 214113 (msedge): 8
PID 225380 (msedge): 8
PID 225393 (msedge): 8
PID 225399 (msedge): 8
PID 225653 (msedge): 8
PID 225672 (msedge): 8
PID 225725 (msedge): 8
PID 225736 (msedge): 8
PID 225759 (msedge): 8
PID 225863 (msedge): 8
PID 226591 (msedge): 8
PID 226917 (msedge): 8
PID 235885 (msedge): 8
PID 242297 (msedge): 7
PID 311605 (msedge): 8
PID 315188 (msedge): 8
PID 360039 (msedge): 8
PID 365091 (msedge): 11
PID 365151 (msedge): 8
PID 366486 (msedge): 8
PID 366662 (msedge): 8
PID 366699 (msedge): 8
PID 367194 (msedge): 8
PID 392834 (chrome): 30
PID 392853 (chrome): 0
PID 392854 (chrome): 0
PID 392857 (chrome): 0
PID 392889 (chrome): 12
PID 392891 (chrome): 7
PID 392896 (chrome): 6
PID 392917 (chrome): 8
PID 392963 (chrome): 8
PID 392971 (chrome): 11
PID 393004 (chrome): 2
PID 393046 (chrome): 8
PID 393120 (chrome): 8
PID 393153 (chrome): 8
PID 393184 (chrome): 6
PID 393252 (chrome): 8
PID 393253 (chrome): 8
PID 393295 (chrome): 8
PID 393378 (chrome): 8
PID 393584 (chrome): 7
PID 394059 (chrome): 8
PID 394993 (chrome): 8
PID 397403 (msedge): 8
PID 397979 (chrome): 8
PID 398344 (chrome): 6
PID 398345 (msedge): 6
PID 458539 (chrome): 8
PID 650094 (msedge): 8
PID 652291 (msedge): 8
PID 654085 (msedge): 8
ls: cannot access '/proc/654266/fd': No such file or directory
PID 654266 (): 0

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to