Bug 489157 - Discover crashes if I try to update too many apps at the same time
Summary: Discover crashes if I try to update too many apps at the same time
Status: RESOLVED WORKSFORME
Alias: None
Product: Discover
Classification: Applications
Component: discover (other bugs)
Version First Reported In: 5.27.5
Platform: Other Linux
: NOR crash
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-06-25 04:30 UTC by Matt Schoen
Modified: 2024-07-10 20:09 UTC (History)
2 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Matt Schoen 2024-06-25 04:30:22 UTC
***
If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org

If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***

SUMMARY
Discover crashes if I try to update too many apps at the same time. I'm able to update one-by-one, but if I just click update all it crashes. At the time, I had 52 updates pending, and I've been whittling it down. I'm not sure what the threshold is but it seems to be related to the # of apps, or maybe their aggregate size.

STEPS TO REPRODUCE
1. 
2. 
3. 

OBSERVED RESULT


EXPECTED RESULT


SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
Comment 1 Nate Graham 2024-06-25 15:17:05 UTC
As the placeholder text says:

> If you're reporting a crash, attach a backtrace with debug symbols;
> see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
Comment 2 Matt Schoen 2024-06-27 05:02:38 UTC
I'm unable to replicate the issue now that I've updated my software. Is there a log somewhere that may have recorded previous crash stack traces?
Comment 4 Matt Schoen 2024-06-28 05:01:46 UTC
I read that document. It looks like I need to launch the app with gdb or valgrind and then trigger the crash. I can no longer replicate the crash now that I've updated my applications. If this happens again in the future I'll be sure to get a stack trace.
Comment 5 Nate Graham 2024-07-10 20:09:39 UTC
Thanks!