exoplanets plugin causes CTD

Can't confirm crash.

Not sure what else to do.

Disabling Exoplanets plugin is a fix. Turning off exoplanet updates also works, provided the file has not been updated yet. Highly repeatable. But nothing odd or relevant seems to show in the log.

It's not the act of updating. Something is different about the old file vs. the new/update file that the plugin doesn't like.

I've installed 0.12.7 and tried update a data - without problem (after restart also).

Alex try this.

1- Go to the exoplanets plugin, and uncheck "Show exoplanets button on toolbar"
2- Exit out of stellarium
3- Restart
4- Exit out
5- CTD!

Seems this behavior happens with the large file from the internet update. With the smaller file that comes with the default install doesn't do this.

If you can't get CTD, make sure Navigational Stars are enabled. I can disable all plugins, but these two together cause the problem. Just figured that condition out now.

Can't reproduce it.

Is the problem still exists in version 0.12.9?

It happens when:
Navigational Stars plugin is enabled.
Exoplanets plugin enabled.
Show exoplanets button on toolbar is disabled
After an update using the 1.1MB internet-provided data file for exoplanets.

All of the above requirements have to be met. And you may need to exit out of stellarium after changing the settings, and restart it. Then the second time it should CTD.

Additionally, clicking on the sextant for navigation stars will also CTD.

If you can't dupe it, then consider it a quirk of "this old PC". I'll just work around it. It's a rather specific and niche crash.

I can confirm:
0.12.9 on Windows
Enable NavStars and Exoplanets plugin. Restart Stellarium.
Configure as Keatah has described: disable display of Exoplanet button. Store settings, exit.
Delete modules/Exoplanets/exoplanets.json
Restart Stellarium.
Activate NavStars. Crash.

It now even crashed after reactivating the display of the Exoplanet button and pressing NavStars display. I don't know what one plugin has to do with the other?

However, 0.12 downloads are much less than 1% of downloads. Some bugs like this will remain in the 0.12 series, while we should concentrate on real progress. I hope 0.16 does not show these issues (and have not seen them.)

I vote for closing this.