Bug 428175 - Discover process keeps on running even after the window is closed
Summary: Discover process keeps on running even after the window is closed
Status: RESOLVED UPSTREAM
Alias: None
Product: Discover
Classification: Applications
Component: discover (show other bugs)
Version: 5.20.1
Platform: Neon Linux
: VHI normal
Target Milestone: ---
Assignee: Dan Leinir Turthra Jensen
URL: https://github.com/fwupd/fwupd/issues...
Keywords:
: 404783 419968 431892 (view as bug list)
Depends on:
Blocks:
 
Reported: 2020-10-24 12:23 UTC by Riccardo Robecchi
Modified: 2021-01-21 19:56 UTC (History)
7 users (show)

See Also:
Latest Commit: https://commits.kde.org/discover/96959195ba6f9755f6a061f0f2825e7783191715
Version Fixed In: 5.20.4
Sentry Crash Report:

Attachments
Multiple Discover processes did not close (110.51 KB, image/png)
2020-10-24 12:23 UTC, Riccardo Robecchi 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Riccardo Robecchi 2020-10-24 12:23:16 UTC 
Created attachment 132683 [details]
Multiple Discover processes did not close

SUMMARY
Discover's process keeps on running even after the window is closed and cannot be closed unless using KSysGuard, leading to memory not being freed. 

STEPS TO REPRODUCE
1. Update packages
2. Close Discover's window

OBSERVED RESULT
The Discover process keeps on running in the background.

EXPECTED RESULT
The Discover process is terminated.

SOFTWARE/OS VERSIONS
Linux: KDE neon Focal
KDE Plasma Version: 5.20.1
KDE Frameworks Version: 5.75.0
Qt Version: 5.15

ADDITIONAL INFORMATION
This happens on both my desktop and my laptop and appears to be triggered after I update packages; if I open Discover from the menu and close it, it works as intended. If I update packages multiple times, multiple processes linger around leading to the situation in the screenshot where almost 1 GB of memory is occupied by Discover's processes. Terminating them appears to cause no issues.
Comment 1 Nate Graham 2020-10-26 15:16:50 UTC 
Can confirm. This is really really annoying. Not only does it waste RAM, but it can prevent Discover from launching later, because technically it's still running (even if that instance has no visible GUI).
Comment 2 Nate Graham 2020-11-07 15:21:08 UTC 
*** Bug 404783 has been marked as a duplicate of this bug. ***
Comment 3 Nate Graham 2020-11-07 15:21:24 UTC 
This is a contributor to slow shutdowns/logouts.
Comment 4 Nate Graham 2020-11-09 22:26:23 UTC 
*** Bug 419968 has been marked as a duplicate of this bug. ***
Comment 5 Aleix Pol 2020-11-18 02:22:10 UTC 
https://github.com/fwupd/fwupd/issues/2600
Comment 6 Bug Janitor Service 2020-11-18 03:59:04 UTC 
A possibly relevant merge request was started @ https://invent.kde.org/plasma/discover/-/merge_requests/53
Comment 7 Nate Graham 2020-11-18 22:56:59 UTC 
Fixed by Aleix Pol Gonzales with https://commits.kde.org/discover/96959195ba6f9755f6a061f0f2825e7783191715 in Plasma 5.20.4!
Comment 8 Aleix Pol 2020-11-18 23:02:52 UTC 
This requires bumping dependencies...
Comment 9 Nate Graham 2020-11-19 19:03:24 UTC 
So that got reverted, but the upstream issue was fixed, in the end! See https://github.com/fwupd/fwupd/issues/2600

FWIW I still think your change makes sense at least for the master branch.
Comment 10 Lua 2020-12-31 14:36:40 UTC 
Is there a way to trigger a task kill whenever Discover window is closed?
Comment 11 Nate Graham 2020-12-31 15:16:39 UTC 
This bug is already fixed upstream in fwupd, so if you're still experiencing it, you should bug your distro to update their fwupd version.
Comment 12 Lua 2020-12-31 16:46:41 UTC 
Unfortunately I'm stuck in KDE 5.19.5 because I use Kubuntu. Is there a way to trigger a task kill in the shutdown process? It's a really annoying bug.
Comment 13 top.lamp4866 2021-01-21 19:56:34 UTC 
*** Bug 431892 has been marked as a duplicate of this bug. ***