https://bugs.kde.org/show_bug.cgi?id=474944
Bug ID: 474944
Summary: High CPU usage when closing Discover after installing
Firefox
Classification: Applications
Product: Discover
Version: 5.27.8
Platform: Archlinux
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: Flatpak Backend
Assignee: plasma-b...@kde.org
Reporter: be...@igalia.com
CC: aleix...@kde.org, jgrul...@redhat.com,
trav...@redhat.com
Target Milestone: ---
Created attachment 161914
--> https://bugs.kde.org/attachment.cgi?id=161914&action=edit
Stack trace
SUMMARY
I noticed that when you close Discover after installing Firefox the
"plasma-discover" process keeps running using a lot of CPU for a minute or two.
This does not happen with all apps, but it can be reproduced with Firefox (and
also with other popular apps like VLC and Gimp).
STEPS TO REPRODUCE
1. Open Discover
2. Search for Firefox (Flatpak) and open the package page (the one that shows
the screenshots, version, size, license, ...)
3. Press "Install" on the top right corner
4. Wait for the installation to finish.
5. Close Discover
6. Open a terminal and look for running processes (with 'top' or similar)
OBSERVED RESULT
The "plasma-discover" process keeps running for a minute or two using a lot of
CPU
EXPECTED RESULT
The "plasma-discover" process dies shortly after closing the Discover window.
SOFTWARE/OS VERSIONS
OS: Arch Linux
KDE Plasma version: 5.27.8
KDE Frameworks version: 5.110.0
Qt version: 5.5.10
Discover: 5.27.8
ADDITIONAL INFORMATION
I'm attaching a stack trace of the running plasma-discover process after the
main window is closed.
>From the high number of QQuickItemPrivate::derefWindow() calls it seems that a
large number of widgets are being destroyed.
I haven't debugged it but Firefox in particular has almost 2000 reviews on
Flathub, and I have a have a hunch that this might be the cause of the problem
(is Discover preloading them or something?).
On a second test, installing Firefox directly from the Discover search results
(i.e. without opening the page) does not seem to cause this problem.
--
You are receiving this mail because:
You are watching all bug changes.
