Summary: | Image Planner crash | ||
---|---|---|---|
Product: | [Applications] kstars | Reporter: | Mark Casazza <markcasazza> |
Component: | general | Assignee: | Jasem Mutlaq <mutlaqja> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | hymur67 |
Priority: | NOR | Keywords: | drkonqi |
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Kubuntu | ||
OS: | Linux | ||
Latest Commit: | 25d7ea35e06ed885455c48864b53d554ed68de4a | Version Fixed In: | |
Sentry Crash Report: | |||
Attachments: | attachment-2180463-0.html |
Description
Mark Casazza
2024-12-28 18:56:17 UTC
Mark, Are you able to reproduce this crash, or did it happen once and is now not crashing? Can you tell if the Imaging Planner was done loading its catalog when it crashed? Hy Created attachment 176984 [details] attachment-2180463-0.html It is not repeating. I don't know if the catalogs were loaded, but I was able to start a catalog search and see results. Mark Casazza http://casazza.net Home of the Clear Sky Alarm Clock and Tonight's Sky On Mon, Dec 30, 2024 at 7:54 PM Hy <bugzilla_noreply@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=497995 > > Hy <hymur67@gmail.com> changed: > > What |Removed |Added > > ---------------------------------------------------------------------------- > CC| |hymur67@gmail.com > > --- Comment #1 from Hy <hymur67@gmail.com> --- > Mark, > Are you able to reproduce this crash, or did it happen once and is now not > crashing? > Can you tell if the Imaging Planner was done loading its catalog when it > crashed? > Hy > > -- > You are receiving this mail because: > You reported the bug. Mark, I was able to occasionally crash the Imaging Planner by (1) removing all the data in the user catalog, (2) restarting KStars and starting the Imaging Planner, and (3) while it was re-loading the catalog and finding various items I'd click randomly on the UI and/or resize the window. The reason for step 1 is that the tool caches what it finds on its catalog load into the user catalog, and so loading on tool startup is much quicker after the initial load, and so it's hard to crash the system since the load is quick. When the user catalog is cleared the load is "slow" again and it's easier to crash it. I really don't understand what causes these crashes (e.g. possible that it's an issue inside the Qt libraries, or possibly a flaw in the planner that I can't find) but I made a change that basically disallowed user input while a catalog is loading and now cannot crash the tool using the above technique. (That's ok, as the user should really wait for the load before interacting with the Imaging Planner anyway.) This is now submitted into the latest code with this merge request: https://invent.kde.org/education/kstars/-/merge_requests/1397 and should be part of the next release at the end of January 2025. Thanks for your report, Hy |