×

INDI Library v2.0.6 is Released (02 Feb 2024)

Bi-monthly release with minor bug fixes and improvements

Kstars 3.5.0 OSx

  • Posts: 2876
  • Thank you received: 809

Replied by Rob Lancaster on topic Kstars 3.5.0 OSx

You said that was somehow related to a QPixmap I think correct? I was not able to replicate the crash myself. Based on what you said, there must be an issue with a QPixmap that doesn't exist. The Summary Screen displays several of these that update regularly, it would be good to know which one might be causing a problem. I would suspect one of the ones shown in this screenshot:



3 years 4 months ago #63172
Attachments:

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

  • Posts: 2876
  • Thank you received: 809

Replied by Rob Lancaster on topic Kstars 3.5.0 OSx

There were 4 QPixmaps shown in that picture, I should say that. The Align Star Profile, the Align Star, the Guide Graph, and the Guide Star.
3 years 4 months ago #63173

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

  • Posts: 179
  • Thank you received: 16

Replied by AirBourn on topic Kstars 3.5.0 OSx

Yes - most (all but two) of the segmentation faults are call chains that end in QPixmap:: or QLabel:: setting a QPixmap. Here are three separate crash reports.
After seeing your posted pictures of QPixmaps (especially the focus curve) it struck me that I recently added an EAF to this rig. That might explain why I'm seeing these crashes now, and not before with previous v3.5.0 builds. So, if the focus curve is a QPixmap, I would definitely start digging there!
Termination Signal:    Segmentation fault: 11
Termination Reason:    Namespace SIGNAL, Code 0xb
Terminating Process:   exc handler [92038]
 
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   org.qt-project.QtGui          	0x000000010c7f9bbd QPixmap::cacheKey() const + 13
1   org.qt-project.QtWidgets      	0x000000010c2d9ec5 QLabel::setPixmap(QPixmap const&) + 37
2                                 	0x0000000109c3f54f 0x10937a000 + 9196879
3   org.qt-project.QtWidgets      	0x000000010c1e445c QWidget::event(QEvent*) + 1132
4   org.qt-project.QtWidgets      	0x000000010c28b18b QFrame::event(QEvent*) + 43
5   org.qt-project.QtCore         	0x000000010cf1ff71 QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) + 241
6   org.qt-project.QtWidgets      	0x000000010c1aa941 QApplicationPrivate::notify_helper(QObject*, QEvent*) + 241
7   org.qt-project.QtWidgets      	0x000000010c1abd75 QApplication::notify(QObject*, QEvent*) + 581
8   org.qt-project.QtCore         	0x000000010cf1fca6 QCoreApplication::notifyInternal2(QObject*, QEvent*) + 166
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   org.qt-project.QtWidgets      	0x0000000110d16844 QLabel::setPixmap(QPixmap const&) + 20
1                                 	0x000000010e6d1fef 0x10dde9000 + 9342959
2   org.qt-project.QtWidgets      	0x0000000110c20379 QWidget::event(QEvent*) + 1129
3   org.qt-project.QtWidgets      	0x0000000110cc7b6b QFrame::event(QEvent*) + 43
4   org.qt-project.QtCore         	0x000000011196aa4e QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) + 206
5   org.qt-project.QtWidgets      	0x0000000110be6588 QApplicationPrivate::notify_helper(QObject*, QEvent*) + 248
6   org.qt-project.QtWidgets      	0x0000000110be79d5 QApplication::notify(QObject*, QEvent*) + 581
7   org.qt-project.QtCore         	0x000000011196a7b4 QCoreApplication::notifyInternal2(QObject*, QEvent*) + 212
8   org.qt-project.QtWidgets      	0x0000000110c194ce QWidgetPrivate::sendPendingMoveAndResizeEvents(bool, bool) + 270
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   org.qt-project.QtWidgets      	0x000000011228a844 QLabel::setPixmap(QPixmap const&) + 20
1                                 	0x000000010fc3cfef 0x10f354000 + 9342959
2   org.qt-project.QtWidgets      	0x0000000112194379 QWidget::event(QEvent*) + 1129
3   org.qt-project.QtWidgets      	0x000000011223bb6b QFrame::event(QEvent*) + 43
4   org.qt-project.QtCore         	0x0000000112ee2a4e QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) + 206
5   org.qt-project.QtWidgets      	0x000000011215a588 QApplicationPrivate::notify_helper(QObject*, QEvent*) + 248
6   org.qt-project.QtWidgets      	0x000000011215b9d5 QApplication::notify(QObject*, QEvent*) + 581
7   org.qt-project.QtCore         	0x0000000112ee27b4 QCoreApplication::notifyInternal2(QObject*, QEvent*) + 212
8   org.qt-project.QtWidgets      	0x000000011218d4ce QWidgetPrivate::sendPendingMoveAndResizeEvents(bool, bool) + 270
3 years 4 months ago #63176

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

  • Posts: 2876
  • Thank you received: 809

Replied by Rob Lancaster on topic Kstars 3.5.0 OSx

Right, but the real question is what sequence of events led to the crash and also which pixmap caused the crash. In order to investigate, we really need you to try different circumstances to see what could lead to the issue. And in terms of the crash log you provided, maybe we need to trace that farther up the call tree, because what you shared is all internal QT calls and we really can't get any info about what led to the crash from that, just that a pixmap it tried to set might not exist. But it would be really helpful to trace that further up the tree to see which one didn't exist. Was it when it was trying to set the pixmap for the guide star for instance?
3 years 4 months ago #63178

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

  • Posts: 2876
  • Thank you received: 809

Replied by Rob Lancaster on topic Kstars 3.5.0 OSx

Tracing up the call for the crash may or may not help though, because I do note that it says "moveandresize" event, which might mean that the setting of the pixmap was in response to trying to change the size of the window or moving it, in which case that might not be a call made by KStars. So really I think we need to know which one is the culprit.

My recommendation is to try the following:

1. Start up KStars Do a whole bunch of focusing slewing around, and focusing again. Keep switching back to that Summery Screen and resizing and moving it and see if you can get it to crash.

2. Restart kstars. Don't try focusing. just start up guiding. Guide a lot. Keep switching back to that Summery Screen and resizing and moving it and see if you can get it to crash.

3. Are you using PHD2 or Internal Guider? If you are using one, try the other. Guide a lot. Keep switching back to that Summery Screen and resizing and moving it and see if you can get it to crash.

It would be very important to totally restart KStars between each trial because we want to identify which pixmap or set of pixmaps might be causing the problem.
3 years 4 months ago #63179

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

  • Posts: 179
  • Thank you received: 16

Replied by AirBourn on topic Kstars 3.5.0 OSx

Here are three crash log files so you can see the entire call chain. In each case, I was running a capture sequence job - so in the middle of a job (internal guiding, offset focusing for filters, no rotations) and checking on status, so I look at where I am in the sequence on the Capture tab, and then switch to the Summary tab to check on time remaining and boom. Sometimes, I'd be in another application, and click the window title bar to activate, then click the Summary and boom. My guess it's a null pointer in there somewhere, because the app just IMMEDIATELY disappears with the crash. No hangs, no spinning beachball, just disappears as if I selected the "Hide" menu item.

File Attachment:

File Name: kstars_202...1-21.txt
File Size:117 KB

File Attachment:

File Name: kstars_202...21-2.txt
File Size:123 KB

File Attachment:

File Name: kstars_202...1-21.txt
File Size:126 KB
3 years 4 months ago #63182

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

  • Posts: 2876
  • Thank you received: 809

Replied by Rob Lancaster on topic Kstars 3.5.0 OSx

Yep, as I was suspecting, this appears to be during a Qt call due to a resizing of the window or something like that, not a direct KStars call. So I think the problem is probably that a pixmap did not get set or something and then when QT tries to redisplay it, the pixmap is not there.

Yes I agree its probably null, but the question is which one is not getting set properly
3 years 4 months ago #63187

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

  • Posts: 179
  • Thank you received: 16

Replied by AirBourn on topic Kstars 3.5.0 OSx

Does the focus pixmap display at all if you don't have a focuser (or just a static placeholder maybe)? I never saw this error before I added the EAF. If that's the case, I'd definitely look into the focus pixmap first.
3 years 4 months ago #63194

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

  • Posts: 460
  • Thank you received: 69

Replied by Jerry Black on topic Kstars 3.5.0 OSx

I have a problem simply compiling kstars on OS X (Big Sur). I have attempted to follow the instructions at github.com/rlancaste/KStars-INDI-Mac-Dev
Not sure what my problem is. Stelllar Solver has not been previouly installed on this machine.

KStars 3.5.0 Beta Build: 2020-11-20T20:42:55Z is installed, but also does not solve. The GSC is installed for the simulator.
-- Found KF5: success (found version "5.67.0") found components: Auth Config Crash DocTools WidgetsAddons NewStuff I18n KIO XmlGui Plotting Notifications 
-- Found CFITSIO: /Volumes/Data_Raid/ASTRO-ROOT/lib/libcfitsio.dylib
-- Found INDI: , /Volumes/Data_Raid/ASTRO-ROOT/include/libindi
-- Found INDI Client Library: /Volumes/Data_Raid/ASTRO-ROOT/lib/libindiclient.a
-- Found INDI: /Volumes/Data_Raid/ASTRO-ROOT/lib/libindiclient.a, /Volumes/Data_Raid/ASTRO-ROOT/include/libindi
CMake Error at /Volumes/Data_Raid/ASTRO-ROOT/lib/cmake/StellarSolver/StellarSolverConfig.cmake:79 (message):
  The imported target "StellarSolver::stellarsolver" references the file
 
     "/Volumes/Data_Raid/ASTRO-ROOT/lib/libstellarsolver.1.5.dylib"
 
  but this file does not exist.  Possible reasons include:
 
  * The file was deleted, renamed, or moved to another location.
 
  * An install or uninstall procedure did not complete successfully.
 
  * The installation package was faulty and contained
 
     "/Volumes/Data_Raid/ASTRO-ROOT/lib/cmake/StellarSolver/StellarSolverConfig.cmake"
 
  but not all the files it references.
Last edit: 3 years 4 months ago by Jerry Black.
3 years 4 months ago #63226

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

  • Posts: 179
  • Thank you received: 16

Replied by AirBourn on topic Kstars 3.5.0 OSx

I just did a new pull on Rob's build script and saw a few updates. Modified the build-env.sh to point to my Qt directory (5.15.1), and did a setup.sh -r (but did not remove the Brew packages). I also already had my own fork of the KStars repository, but unsure if that was necessary for this build or not. It successfully built the KStars app on Big Sure (11.0.1) with the XCode 12 tools! Good work, Rob!

Curiously, what didn't happen, was a build of Ekos. I'm now going to look through the doc again and figure out why. Rob - do you have the easy answer for building Ekos?

Here's what the Libraries tab in the About KStars dialog says:
3 years 4 months ago #63232
Attachments:

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

  • Posts: 2876
  • Thank you received: 809

Replied by Rob Lancaster on topic Kstars 3.5.0 OSx

I agent fully restored the functionality of the scripts yet, but I am getting close I think.

Jerry you might try again, I fixed that one this afternoon
3 years 4 months ago #63237

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

  • Posts: 2876
  • Thank you received: 809

Replied by Rob Lancaster on topic Kstars 3.5.0 OSx

To try again fresh you can use the -r option or you can delete the astroroot and build folders in the project folder
3 years 4 months ago #63238

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

Time to create page: 0.409 seconds