Bug 391437 - plasmashell eat up 100% CPU with likely buggy electron application
Summary: plasmashell eat up 100% CPU with likely buggy electron application
Status: RESOLVED UPSTREAM
Alias: None
Product: plasmashell
Classification: Plasma
Component: Global Menu widget (show other bugs)
Version: 5.12.2
Platform: Other Linux
: NOR normal
Target Milestone: 1.0
Assignee: Kai Uwe Broulik
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-03-05 14:06 UTC by Kevin Ottens
Modified: 2018-03-05 16:14 UTC (History)
1 user (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Kevin Ottens 2018-03-05 14:06:18 UTC
I noticed that happening only when I have the rocket.chat electron app running. I can't tell if it's more widespread or not.

In any case this application seems to be doing something our global menu facilities don't expect. When I have it running after a few switch between windows, plasmashell then eats up 100% cpu until I quit it.

On the standard error I see the following output repeated infinitely at a very fast pace:
Unhandled property update "children-display"
Comment 1 Kai Uwe Broulik 2018-03-05 14:54:03 UTC
https://github.com/electron/electron/issues/8455
Comment 2 Kevin Ottens 2018-03-05 15:59:32 UTC
Still, shouldn't such a central facility defend itself from getting in such a mess than eating 100% CPU because of a buggy application? For sure more buggy applications and more applications on older revisions of Electron exist.
Comment 3 Kai Uwe Broulik 2018-03-05 16:05:44 UTC
„Bundle everything, they said, it's the future, they said“.

I have never seen any app exhibit this other than Electron-based ones so I'm not going to spend time working around their broken stack or eco system, if I had, they would have never fixed this in the first place. (Patches welcome of course)
Comment 4 Kevin Ottens 2018-03-05 16:14:23 UTC
Fair enough, I'd have expected more than just the bloody electron app having this nasty "spam notification" issue. If it's just them it's likely OK indeed.