Closed Jusas closed 2 years ago
Yes, I think Jasem needs to fix the forum. I don't know what happened. We have been using it for years with no issues. . .
I will definitely check out this one. Actually, Wolfgang mentioned it to me this morning as well where it crashes in the same spot. So it definitely needs to be addressed. But so far, I can't seem to replicate it myself. Every time it solves just fine for me.
Ok I understand what was going now now. On some systems the pointer wasn't initialized to a nullptr, but on mine it was. So I didn't see any crashes but others did sometimes. As a solution, I got rid of the new keyword and made it not a pointer, so now there should be no issue.
Please check
Yeah that was it, it works now! No more crashes. Perfect!
Oh and for the record, I'm testing in Linux (Kubuntu 20.04). I'm guessing you're running MacOS.
Correct.
ok glad to hear it. Keep testing. We want to release the next version of KStars soon, and so want to make sure everything is good first.
I think Jasem has fixed the forum as well.
Hi Rob, sorry for posting this here but the Indilib forums are somehow broken and I can't seem to reply to the StellarSolver 2.0 thread no matter what I do. Referring to https://indilib.org/forum/ekos/11388-announcing-stellarsolver-2-0/81108.html#81108
So I decided to bring my business here ;)
I just ran the scenarios again. The crash when using external solver and stopping Indi has been fixed by the changes. š
The new Watney settings look good as well. š
The crash using the internal solver changed a bit:
Steps to reproduce:
--> SIGSEGV
The line in question:
Also weirdly enough as I now tried to reproduce it a second time, it already crashes on first solve. Not sure how it managed to run the first solve the first time just fine.