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

            Bug ID: 471642
           Summary: Severe memory leak in 5.27.5 with Wayland
    Classification: Plasma
           Product: plasmashell
           Version: 5.27.6
          Platform: Archlinux
                OS: Linux
            Status: REPORTED
          Severity: major
          Priority: NOR
         Component: general
          Assignee: plasma-b...@kde.org
          Reporter: mich...@butash.net
                CC: k...@davidedmundson.co.uk
  Target Milestone: 1.0

Created attachment 159983
  --> https://bugs.kde.org/attachment.cgi?id=159983&action=edit
Memory Leak Graph, running x11, reboot, running wayland plasma

SUMMARY
After switching back to testing using wayland over x, I noticed my system
suddenly using all 128gb of ram and going into swap.  Plasmashell is consuming
all of the memory, and I have to restart back to sddm.

STEPS TO REPRODUCE
1. Log into Plasma Wayland session from x, start desktop
2. Start normal use (browsers, gaming, zoom, libreoffice)

OBSERVED RESULT
Within 2 days, all 128gb of my ram is consumed of what is left by plasmashell
process.  Restarting the session is necessary.

EXPECTED RESULT
I normally operate weeks/months without reboot with x11, and have with wayland
on earlier 5.27.1 or so, but since last upgrade(s) and testing with 5.27.5 and
.6 now, there is an extreme memory leak directly in plasmashell.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Arch Linux, 6.3.9 kernel, nvidia 535.54.03, wayland 1.22.0
KDE Plasma Version: 5.27.6
KDE Frameworks Version: 5.107.0
Qt Version: qt5-5.15.10

System uses a large 11520x2160p frame buffer with 3x 4k displays, has caused
even x11 issues earlier kde5, but lately not a problem over time with x11 on
the 3080rtx gpu, only with wayland.

ADDITIONAL INFORMATION
With plasma wayland session or x11 (both same), I use NO desktop widgets, only
the default taskbar, k menu, systray, and latte-dock with various widgets
loaded there.  The plasmashell process itself is consuming the memory from htop
observation.  I had been using wayland for some weeks a few months ago without
issue, went back to xorg for a bit after some odd crashes, only this last week
trying wayland again to now observe these.  I added my desktop to librenms for
snmp polling to observe/document the memory use as well, will include this of
the past week after using xorg (normal use), and then switching back to wayland
observing the drastic leak.

I'm willing to provide any requested info, and willing to run with valgrind if
possible, not sure the best way to do this and actually use the desktop.

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

Reply via email to