Bug 392668 - Memmory hog after constant use
Summary: Memmory hog after constant use
Status: RESOLVED DUPLICATE of bug 368838
Alias: None
Product: plasmashell
Classification: Plasma
Component: general (show other bugs)
Version: master
Platform: Gentoo Packages Linux
: NOR normal
Target Milestone: 1.0
Assignee: David Edmundson
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-04-03 08:07 UTC by Zakhar
Modified: 2018-04-11 00:43 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
ps aux --sort -rss (17.99 KB, text/plain)
2018-04-03 08:07 UTC, Zakhar
Details
Look at that usage (460.34 KB, image/png)
2018-04-07 06:09 UTC, Zakhar
Details
kquitapp5 plasmashell && QSG_INFO=1 && plasmashell (7.76 KB, text/plain)
2018-04-10 05:02 UTC, Zakhar
Details
large mem usage (15.19 KB, text/plain)
2018-04-11 00:16 UTC, Zakhar
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Zakhar 2018-04-03 08:07:43 UTC
Created attachment 111796 [details]
ps aux --sort -rss

After about 1.5 hours of constant use of KDE I noticed plasmashell hogging great a great deal of ram. Let me know what I can do to further acquire data to help patch these memory leaks.
Comment 1 Zakhar 2018-04-03 08:11:12 UTC
Using latest KDE available.
Comment 2 Zakhar 2018-04-03 08:11:38 UTC
Using plasmashell 5.12.4
Comment 3 Nate Graham 2018-04-03 14:21:24 UTC
Smells like Bug 368838.

Do you use a slideshow for your wallpaper or in a media frame widget? Do you notice it happening when you move through the categories of the Application Launcher or Application Menu?
Comment 4 Zakhar 2018-04-04 04:57:16 UTC
No slide show, desktop is not set to folder mode rather to desktop mode displaying a single non animated image.
Comment 5 Zakhar 2018-04-04 04:57:40 UTC
Just one image, no image rotation is set.
Comment 6 Nate Graham 2018-04-04 20:36:52 UTC
Thanks for the info. It would be helpful if you can do a bit of sleuthing and try to find a reproducible way to make the problem occur (or not occur!)
Comment 7 Zakhar 2018-04-04 21:38:04 UTC
I can easily make mem usage climb, I just don't now how to log or profile it. Let me know the tools and cli arguments, then I will start to reproduce it with profiling tools running.
Comment 8 Nate Graham 2018-04-04 21:48:35 UTC
I'll let one of the more experienced Plasma developers chime in with that information.
Comment 9 Zakhar 2018-04-04 22:13:09 UTC
Im experiencing irreversible memory climbs with KDE with every session. Many times needlessly going to 4-5gb
Comment 10 Zakhar 2018-04-06 05:46:23 UTC
Its likely due to the fact Im using about 10 desktop widgets. But I have no way to collect meaningful data untill someone shows me how.
Comment 11 Zakhar 2018-04-07 06:06:58 UTC
I am confirming this because after leaving KDE idling for a few hours I returned home to see it taking more than 7 of the 8GB total ram I have and more than 1GB or swap, meaning it surpassed hardware ram limit. Please address this somehow.
Comment 12 Zakhar 2018-04-07 06:09:07 UTC
Created attachment 111882 [details]
Look at that usage

Unusable.
Comment 13 David Edmundson 2018-04-08 11:48:30 UTC
The status is for devs when we have all the information we need. 

Please include output of 
kquitapp5 plasmashell
QSG_INFO=1 plasmashell
Comment 14 David Edmundson 2018-04-09 21:52:34 UTC
marking as waiting for info
Comment 15 Zakhar 2018-04-09 22:04:14 UTC
Do do NOT know how to include required stuff. Please specify applicable commands/methods.
Comment 16 David Edmundson 2018-04-09 22:06:54 UTC
In a terminal


kquitapp5 plasmashell
QSG_INFO=1 plasmashell

paste output here
Comment 17 Zakhar 2018-04-10 05:02:56 UTC
Created attachment 111934 [details]
kquitapp5 plasmashell && QSG_INFO=1 && plasmashell

No programs were loaded at time of running suggested commands.
Comment 18 Zakhar 2018-04-10 05:08:50 UTC
Memory usage was at about 3.8GB with no programs running, then I ran commands.
Comment 19 Zakhar 2018-04-11 00:16:26 UTC
Created attachment 111942 [details]
large mem usage
Comment 20 David Edmundson 2018-04-11 00:43:04 UTC
>qt.scenegraph.general: QSG: basic render loop

Thanks

*** This bug has been marked as a duplicate of bug 368838 ***