×

INDI Library v2.0.7 is Released (01 Apr 2024)

Bi-monthly release with minor bug fixes and improvements

KStars 3.6 crashes when Find Object is selected

  • Posts: 84
  • Thank you received: 6
I have the same problem on Stellarmate/RPi, when I try to use the search function in kStars or in the scheduler, kStars crash and restarts, It’s 32bit Stellarmate 1.7.2, kStars 3.6.0.
Last edit: 1 year 8 months ago by Keld Henningsen.
1 year 8 months ago #85300

Please Log in or Create an account to join the conversation.

  • Posts: 209
  • Thank you received: 29
Not sure if I should continue to post here or file a bug report but I'm attaching a cut and paste of the log file that Apple generates when an application crashes. Hoping to image this weekend and will try to use a work around of some sort so that KStars will run.

Clear Skies,
1 year 8 months ago #85301
Attachments:

Please Log in or Create an account to join the conversation.

  • Posts: 2877
  • Thank you received: 812
Hey guys, after some very challenging testing involving a gradual process of elimination this week, I think I have tracked this issue down. It seems to have been caused by this commit:

github.com/KDE/kstars/commit/5a2ba9f8e8b...93a50ca66f09cb2f985d

It was quite hard to track down because any time I launched Kstars from the terminal or from QT Creator on my system, the crash didn't occur, but it did occur whenever I ran it by double clicking it in the latest release. That made it very hard to debug. I had to add a bunch of qMessageBox messages to even see where it was crashing and what was causing it. I think it was caused by something in the constructor for the new Asynch DB that was introduced in this commit.

I found that if I put my QMessageBox in the right spot in the constructor, the crash didn't occur on my Mac. So then I tried replacing that with a sleep command and it seemed to work too. So it isn't a really good solution, but it is a band aid until this can get resolved in a better way. Hopefully it works for everyone.

I just built a new DMG today that should include this change and I uploaded it to the normal download spot for 3.6.0. Please test to see if it is fixed.
The following user(s) said Thank You: Frederick Ruegsegger
1 year 8 months ago #85539

Please Log in or Create an account to join the conversation.

  • Posts: 209
  • Thank you received: 29
Hi Ron - I've just done some quick testing after downloading the new version. Everything seems to be working based on a quick test of Find Object from the main KStars menu as well as from within the telescope control in EKOS. Thanks so much! Will do more with it hopefully tonight and keep you posted.
1 year 8 months ago #85544

Please Log in or Create an account to join the conversation.

  • Posts: 209
  • Thank you received: 29
After the initial success, I have been trying to launch KStars again this evening hoping to get some imaging in tonight. KStars no longer launches. I've reinstalled the KStars update, reinstalled MacOS and each time I try to launch I get the 'spinning beach ball of death' and have to Force Quit KStars. If I can provide any information or system reports, please let me know. If anyone else is having the same problem, would be great to know - trying to sort out whether it's a result of something unique to my system environment.
1 year 8 months ago #85554

Please Log in or Create an account to join the conversation.

  • Posts: 209
  • Thank you received: 29
If it's helpful, I've attached the Mac Problem Report that was generated when I Force Quit KStars.Cheers,

File Attachment:

File Name: ProblemRep...8-21.rtf
File Size:2,959 KB
1 year 8 months ago #85558
Attachments:

Please Log in or Create an account to join the conversation.

  • Posts: 2877
  • Thank you received: 812
Those crash reports aren't usually too helpful, once in awhile they can provide some insight but usually a better thing would be to run it from the terminal with this command:

/Applications/KStars.app/Contents/MacOS/kstars

And see what prints and if you could give some details about what was happening when it crashed that is also more helpful.
1 year 8 months ago #85562

Please Log in or Create an account to join the conversation.

  • Posts: 209
  • Thank you received: 29
Rob - thanks! Here's the text that displays when I run the command you referenced:

Last login: Sun Aug 21 17:15:51 on console
fred@Fredericks-Mac-Studio ~ % /Applications/KStars.app/Contents/MacOS/kstars
Call to writableLocation without an application-based location.
org.kde.kstars: Welcome to KStars 3.6.0 Stable
org.kde.kstars: Build: 2022-08-21T16:15:07Z
org.kde.kstars: OS: "osx"
org.kde.kstars: API: "x86_64-little_endian-lp64"
org.kde.kstars: Arch: "x86_64"
org.kde.kstars: Kernel Type: "darwin"
org.kde.kstars: Kernel Version: "21.6.0"
org.kde.kstars: Qt Version: 5.15.5
Starting DBus

Regarding what was happening when it crashed, it actually simply failed to launch. I would launch KStars and I'd just get the beachball spinning. When I went into Force Quit, it showed up as a non-responsive app. Let me know if I can provide more color.
1 year 8 months ago #85570

Please Log in or Create an account to join the conversation.

  • Posts: 83
  • Thank you received: 13
I can't even get past the splash screen.

When I run the KStars executable from terminal, this is what I get as it runs and after it errors out.
Call to writableLocation without an application-based location.
org.kde.kstars: Welcome to KStars 3.6.0 Stable
org.kde.kstars: Build: 2022-08-21T16:15:07Z
org.kde.kstars: OS: "osx"
org.kde.kstars: API: "x86_64-little_endian-lp64"
org.kde.kstars: Arch: "x86_64"
org.kde.kstars: Kernel Type: "darwin"
org.kde.kstars: Kernel Version: "19.6.0"
org.kde.kstars: Qt Version: 5.15.5
Starting DBus
org.kde.kstars: Processing  "unnamedstars.dat" , HTMesh Level 3
org.kde.kstars:   Sky Mesh Size:  512
org.kde.kstars: Loaded DSO catalog file:  "unnamedstars.dat"
org.kde.kstars: "Star HD20,794 not found."
org.kde.kstars: "Star HD98,230 not found."
org.kde.kstars: Loaded DSO catalogs.
org.kde.kstars: Loading asteroids
libc++abi.dylib: terminating with uncaught exception of type std::out_of_range: unordered_map::at: key not found
zsh: abort      /Applications/KStars.app/Contents/MacOS/kstars
Having fun learning about the cosmos.
I run an astrophotography site as a hobby.
1 year 8 months ago #85571

Please Log in or Create an account to join the conversation.

  • Posts: 403
  • Thank you received: 41
I am on the same page Rob, M1, 12.5
MacBook-Air:~ euripides$ /Applications/KStars.app/Contents/MacOS/kstars
Call to writableLocation without an application-based location.
org.kde.kstars: Welcome to KStars 3.6.0 Stable
org.kde.kstars: Build: 2022-08-21T16:15:07Z
org.kde.kstars: OS: "osx"
org.kde.kstars: API: "x86_64-little_endian-lp64"
org.kde.kstars: Arch: "x86_64"
org.kde.kstars: Kernel Type: "darwin"
org.kde.kstars: Kernel Version: "21.6.0"
org.kde.kstars: Qt Version: 5.15.5
Starting DBus

and freezes not responding.
1 year 8 months ago #85579

Please Log in or Create an account to join the conversation.

  • Posts: 209
  • Thank you received: 29
Rob and others - I was able to run 3.6 on a MacBook Pro (Intel) last night with no problems. This morning I did a routine OS security update to MacOS 12.5.1 and now KStars doesn't run on the MacBook Pro any longer. Maybe something in that security update?
Last edit: 1 year 8 months ago by Frederick Ruegsegger.
1 year 8 months ago #85585

Please Log in or Create an account to join the conversation.

  • Posts: 2877
  • Thank you received: 812
I did a bunch of work on this after work today. There are a couple of different issues it seems. The one issue where it freezes on Dbus seems to have been caused by an issue in my build I think. The other issue where it got this message: "libc++abi.dylib: terminating with uncaught exception of type std::out_of_range: unordered_map::at: key not found" had me really lost for awhile this evening since it happened on a virtual machine I was testing on with both the craft build and with my own build after I fixed the dbus issue. But this error did not occur on my main machine so I was stumped. Then I tried deleting (backing up of course!) my data directory on my main machine and I could finally replicate the issue. So basically it means that there is something corrupted in the data directory in the dmg. This also is a hard bug to detect because most of us have installed kstars before and already have settings in place, but this problem would only show up in a new install. So I don't know when this issue first appeared. but I will go through and see if I can find the issue tomorrow after work.

Thanks for testing!!
The following user(s) said Thank You: Frederick Ruegsegger
1 year 8 months ago #85593

Please Log in or Create an account to join the conversation.

Time to create page: 0.274 seconds