| Summary: | Discover doesn't exit cleanly | ||
|---|---|---|---|
| Product: | [Applications] Discover | Reporter: | Nate Graham <nate> |
| Component: | discover | Assignee: | Dan Leinir Turthra Jensen <leinir> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | normal | CC: | aleixpol |
| Priority: | NOR | ||
| Version First Reported In: | 5.20.90 | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: |
Doesn't exit cleanly
So many threads |
||
Looks like the main process does eventually exit after 30 seconds to a minute. Still it should exit immediately as soon as the main window is closed. can you take a backtrace? You can do it by running it in gdb, closing discover and as it's in this 30s frame press Ctrl+C on gdb then run "thread apply all bt". This should give us a backtrace for every running thread, hopefully will tell us who is keeping us. FWIW I cannot reproduce. Created attachment 135552 [details]
So many threads
So many threads. I'm attaching the backtrace as a text file because it's rather long.
*** This bug has been marked as a duplicate of bug 431319 *** |
Created attachment 135535 [details] Doesn't exit cleanly Everything KDE from git master. See screen recording. When Discover's main window is closed, the process doesn't fully exit. This makes it look like it's not running, but if you try to launch it, it won't launch, because it's already running. Needless to say, this is not an optimal user experience. This started happening to me over the last few weeks. First it happened some of the time, now it's graduated to being 100% reproducible. I'm not sure what changed on my system to provoke this, but whatever it is, Discover is not happy about it.