Bug 378749

Summary: plasmashell: 262 GB virtual memory
Product: [Plasma] plasmashell Reporter: stefano.d
Component: generalAssignee: David Edmundson <kde>
Status: RESOLVED NOT A BUG    
Severity: normal CC: bshah, info, opensource, plasma-bugs-null
Priority: NOR    
Version First Reported In: 5.8.6   
Target Milestone: 1.0   
Platform: Neon   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: htop screenshot
Many instances of plasmashell

Description stefano.d 2017-04-13 17:18:31 UTC
Created attachment 105013 [details]
htop screenshot

plasmashell is allocating 262 GB virtual memory.

I'm using KDE Neon LTS.
Comment 1 stefano.d 2017-04-13 17:23:43 UTC
Created attachment 105014 [details]
Many instances of plasmashell
Comment 2 David Edmundson 2017-04-13 22:27:38 UTC
You have many instances of a lot of things; which means you're running all of KDE in multiple DBus sessions...

That's not in our code.
Comment 3 stefano.d 2017-04-14 07:02:30 UTC
As a user, I don't know who I should contact. Any ideas?
Comment 4 stefano.d 2017-05-01 08:22:53 UTC
Well, again: Who is responsible for this multiple instances?
Comment 5 skierpage 2017-05-12 08:04:23 UTC
It seems there are two bugs here: a) lots of plasmashell processes, and b) an enormous virtual memory size for each one. I filed bug 379739 about enormous virtual size for baloo_file and plasmashell, but there was only one process (with many threads) for each.
Comment 6 stefano.d 2017-05-12 16:00:46 UTC
I'm now aware this has been closed as "RESOLVED INVALID".
Please, look harder: There are not only many instances, but each instance is allocating 292 GB!
As skierpage pointed out: These are two different bugs!
Comment 7 Christoph Feck 2017-05-16 01:56:31 UTC
It is probably the same bug, because plasmashell uses baloo libraries. To confirm, please disable baloo in systemsettings, and reboot.
Comment 8 stefano.d 2017-05-16 05:29:54 UTC
I disabled baloo from the beginning after my KDE Neon installation.
Comment 9 aCandidMind 2017-09-26 17:16:45 UTC
Having exactly the same behavior here as stefano. But as per bug 379739 this seems to be as designed and nothing to worry about. The different entries are threads as I understand it and thus they share the same memory.
Comment 10 David Edmundson 2017-09-27 10:02:38 UTC
Virtual memory use is a non issue.

As for multiple instances, it might be me misreading a screenshot. htop lists each thread separately.

If you think that's happening, please can you confirm with "ps" and reopen this
and attach the output of /proc/PIDHERE/environ of at least two of them.