Bug 395898

Summary:	High CPU usage when Atom text editor is open
Product:	[Plasma] plasmashell	Reporter:	Jake Bornheimer <jacobbornheimer>
Component:	Global Menu widget	Assignee:	Kai Uwe Broulik <kde>
Status:	RESOLVED UPSTREAM
Severity:	normal	CC:	mvourlakos, plasma-bugs-null
Priority:	NOR
Version First Reported In:	5.13.1
Target Milestone:	1.0
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Jake Bornheimer 2018-06-26 17:40:52 UTC

Overview: 

Whenever Atom text editor is opened, latte-dock's CPU usage goes up from <1% to ~25%. At the same time, Atom's usage also reaches around 25%. 

This results in a pronounced slowdown. Minimizing/maximizing windows slows, as well as highlighting when hovering over the dock. This stabilizes after 15-20 seconds. However, the slowdown happens again when hovering over or interacting in any way with the dock.

Can be replicated repeatedly.

Tested with a number of other applications, none of which duplicate this bug.

Steps to Reproduce:

1) install latte-dock via sudo apt install latte-dock
2) install atom via sudo snap install atom
3) open latte-dock
4) open atom

Latte dock installed via apt. Latte version 0.7.4
Atom installed via snap. Atom version 1.27.2.

OS: Kubuntu 18.04, 64-bit
KDE Plasma version 5.12.5
Qt version 5.9.5

Comment 1 Michail Vourlakos 2018-06-26 18:18:01 UTC

are you using global menu?

Comment 2 Michail Vourlakos 2018-06-26 20:00:49 UTC

I reproduced this by using the plasma application menu bar.
The plasmashell process after the atom editor opened was using constantly 100% of one of my processors

Comment 3 Kai Uwe Broulik 2018-06-27 08:11:33 UTC

Please tell Atom to update their Electron version, this has been fixed in Electron more than a year ago: https://github.com/electron/electron/issues/8455

Comment 4 Michail Vourlakos 2018-06-27 12:11:41 UTC

(In reply to Jake Bornheimer from comment #0)
> Overview: 


as mentioned, please report this to atom editor in order to update their libraries...

Comment 5 Christoph Feck 2018-06-27 14:03:00 UTC

Atom developers already track the update issue as https://github.com/atom/atom/pull/17273