Bug 361497 - High memory usage of plasma shell when vmvare workstation is running
Summary: High memory usage of plasma shell when vmvare workstation is running
Status: RESOLVED WORKSFORME
Alias: None
Product: plasmashell
Classification: Plasma
Component: generic-performance (show other bugs)
Version: 5.5.5
Platform: openSUSE Linux
: NOR major
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-04-07 15:10 UTC by Matthias Olschowy
Modified: 2022-12-05 05:14 UTC (History)
5 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Matthias Olschowy 2016-04-07 15:10:33 UTC
VMware Version 12.1.0 build-3272444
VMware Guest Windows 10



Reproducible: Always

Steps to Reproduce:
1. Start VMware Workstation


Actual Results:  
Memory usage of plasma shell: 2.702.592 K
CPU fan is obvioulsy working hard


Expected Results:  
Much less memory and CPU usage
Comment 1 Matthias Olschowy 2016-04-08 11:49:56 UTC
The problem is greatly reduced or even resolved after having VMware Tools reinstalled.
Comment 2 Matthias Olschowy 2016-04-19 13:52:08 UTC
My last comment was not appropriate. The problem still continues on.
Comment 3 Raman Gupta 2017-03-14 16:23:09 UTC
I have the same behavior on Fedora 24 with KDE Plasma 5.8.6, Frameworks 5.31.0, QT 5.6.2, and VMWare 12.5. There are other reports of this as well:

https://forum.manjaro.org/t/plasmashell-kde-high-load-over-my-cpu/8645/5

One commenter at https://superuser.com/questions/1118866/high-load-over-my-cpu-and-high-temperature-when-running-plasmashell had an interesting theory, but I have not yet tested it:

> FWIW, we ran into this at work and it turns out it's the vmware tray icon. If you kill the vmware-tray process after you start up the VMs, then everything is fine. There is an option to say that you don't ever want the icon, but that doesn't appear to be honored and VMWare fires it up anyways.

CPU usage increases to about 60% on plasmashell, with a significant percentage on the Xorg process and on the VMware process, even with an idle VM. Shutting down VMWare has no affect, but restarting plasma after shutting down VMWare fixes the issue.

The display becomes sluggish until plasmashell is restarted.
Comment 4 Raman Gupta 2017-03-15 23:45:42 UTC
Following on my last comment, I believe I can confirm the issue with vmware and plasmashell, at least on my machine, is related to the vmware-tray process. I started vmware and immediately killed the vmware-tray process on my Fedora host. Since that time, no more CPU issues with plasmashell. I'd like to hear from the OP whether or not that is the case for him also.

Now I suspect that vmware is doing something naughty related to the tray... but, I don't believe any program should be able to "break" plasmashell using any tray APIs, no matter what they are. Allowing this is essentially allowing a denial of service attack on plasmashell.
Comment 5 Alexander Mentyu 2018-03-16 16:29:41 UTC
Can't reproduce

plasmashell process uses normal amount of memory when VMware app is running, tray process uses ~1% of CPU and 1% of RAM (8GB)

vmware-workstation 14.1.1-2
Plasma: 5.12.2
Apps: 17.12.2
Frameworks: 5.43.0
Qt: 5.10.1
Kernel: 4.14.25-1-MANJARO
OS: Netrunner Rolling
Comment 6 Nate Graham 2022-11-05 03:29:51 UTC
Thank you for reporting this issue in KDE software. As it has been a while since it was reported, can we please ask you to see if you can reproduce the issue with a recent software version? Like Plasma 5.25, or ideally 5.26?

If you can reproduce the issue, please change the status to "CONFIRMED" when replying. Thank you!
Comment 7 Bug Janitor Service 2022-11-20 05:11:48 UTC
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!
Comment 8 Bug Janitor Service 2022-12-05 05:14:01 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now 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

Thank you for helping us make KDE software even better for everyone!