[kde] [Bug 450600] New: plasma_session memory leak

le_dino bugzilla_noreply at kde.org
Sun Feb 20 06:21:42 GMT 2022


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

            Bug ID: 450600
           Summary: plasma_session memory leak
           Product: kde
           Version: unspecified
          Platform: Other
                OS: Linux
            Status: REPORTED
          Severity: normal
          Priority: NOR
         Component: general
          Assignee: unassigned-bugs at kde.org
          Reporter: palletonde at gmail.com
  Target Milestone: ---

SUMMARY
I've noticed that my system seems to suffer giant memory leaks over time,
coming from process plasma_session. Researching told me that various people
experience this from process plasmashell, but it doesn't seem to be my case as
it's sitting on about 670mb compared to the current 15gb from plasma_session.
Rebooting fixes it but eventually it'll come back.
I don't turn it off overnight (I have my reasons for it) and when I turn the
monitors back on I'm usually welcomed with a series of notifications that say
kde has crashed? I don't know if that has relevance on the issue.

I couldn't tell when this started but it's relatively recent as I can't say
I've seen this happen last month or so. I tried looking in the kde bug tracker
but I'm not experienced with this stuff just yet so I didn't find anything
related to plasma_session memory leaks.
It just keeps increasing and I don't know what to do.
I made a post on reddit which suggested filing a bug report, so here I am

OBSERVED RESULT
Memory usage way too high, growing over 10, 12, 14gb and counting

EXPECTED RESULT
Definitely not >10gb of plasma_session

SOFTWARE/OS VERSIONS
Operating System: Kubuntu 21.10
KDE Plasma Version: 5.24.1
KDE Frameworks Version: 5.91.0
Qt Version: 5.15.2
Kernel Version: 5.13.0-28-generic (64-bit)
Graphics Platform: X11
Processors: 16 × AMD Ryzen 7 3700X 8-Core Processor
Memory: 31.3 GiB of RAM
Graphics Processor: NVIDIA GeForce RTX 2070 SUPER/PCIe/SSE2

-- 
You are receiving this mail because:
You are the assignee for the bug.


More information about the Unassigned-bugs mailing list