After approximately two days of uptime, Xorg starts consuming more memory than it normally should. Xorg usually reaches over 200 MB, and if modifying plasmoids or restarting the 'plasmashell' process frequently it can even go over 400 MB!
Created attachment 102217 [details] Screenshot
Created attachment 102218 [details] Screenshot
Created attachment 102219 [details] top
Created attachment 102220 [details] free
For comparison: After restarting Xorg (control + alt + backspace) and logging back in, Xorg only used about 35 MB. That amount does slowly increase, and it's hard to tell when it does so legitimately or when it might be the result of a leak.
Created attachment 108107 [details] stack trace of memory leak plasma-workspace 4:5.8.6-2.1 xserver-xorg 1:7.7+19 debian stretch
Hi, This might help. My workstation has 256GB of memory, so I had plenty of time to catch plasmashell in the act of chewing up all the memory it could. When I first caught it , it has reached 1.5GB!! This is a brand new install of debian stretch, completely up-to-date (30Sep2017). I attached the debug trace when I attached GDB and saw where it was stuck.
Created attachment 108109 [details] valgrind , shows massive memory allocation. Does not run sufficiently to profiel Valgrind. Some direction of what to look for would help.
Please see the memory leak and upstream Qt bug in 381000
Debian does not use Qt 5.9 yet. Still it would be interesting if a recent version of Qt and/or Plasma makes a difference.
381000 was closed and many Qt updates have happened since then. Mircea, can you please test and confirm if this issue is still occurring or if this bug report can be marked as resolved, thanks.
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!
Haven't seen this one in a long time, definitely safe to assume it was solved by now.