Bug 345348 - KStars crashes when you try to add an object from a newly included custom catalog to the observing list
Summary: KStars crashes when you try to add an object from a newly included custom cat...
Status: RESOLVED WORKSFORME
Alias: None
Product: kstars
Classification: Applications
Component: general (show other bugs)
Version: git
Platform: Compiled Sources Linux
: NOR crash
Target Milestone: ---
Assignee: Akarsh Simha
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-03-20 00:42 UTC by Akarsh Simha
Modified: 2017-08-09 20:17 UTC (History)
2 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Akarsh Simha 2015-03-20 00:42:41 UTC
This has happened a good number of times to me now.

Suppose we create a new custom catalog .cat file and load it into KStars using the "Load Catalog" option in the Settings dialog. Then, check the appropriate checkbox to make the catalog visible. You can now find objects from this catalog etc without any problems.

However, if you open the observing list (Ctrl + L) and try to add the object to the observing wishlist for example, KStars will segfault.

It works fine after a restart, for example, if you restart KStars and then go back to the settings dialog to show the newly added catalogs, then open up the observation planner, things go alright.

Reproducible: Always

Steps to Reproduce:
1. Add a new custom catalog using the "Load Catalog" feature
2. Add an object from the newly loaded catalog to the observation planner without restarting KStars
3. Crash.
Comment 1 Akarsh Simha 2015-03-20 00:43:25 UTC
(Jasem, I might look into it at some point later by myself. Look into it only if you have the time to spare.)

Regards
Akarsh
Comment 2 Akarsh Simha 2015-05-02 09:40:00 UTC
The post here describes the potential cause and a possible solution:
https://mail.kde.org/pipermail/kstars-devel/2015-May/006173.html

Regards
Akarsh
Comment 3 Csaba Kertész 2017-08-09 20:17:16 UTC
This bug is not reproducible anymore.

It was fixed by some other changes or with my recent improvements by using smart pointers for the sky objects.