×

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: 2247
  • Thank you received: 223

Replied by Gonzothegreat on topic Kstars 3.5.0 OSx

Kstars 3.5.0 has been very stable, I was about to put a post about it and then I kid you not 30 sec after I thought about the stability the all thing went batshitcrazy on me. Very spooky.
First time this actual error happened ever. I fixed it after figuring it out, and I'm running 2 sessions now.

One thing that's not quite working well is the guiding, I think I may have a log and will post it another timer, something about exposure timeout.
3 years 4 months ago #62540

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

  • Posts: 2247
  • Thank you received: 223

Replied by Gonzothegreat on topic Kstars 3.5.0 OSx

it just crashed again and messed up the coordinates again, they swapped. I will see if there is a log file...
3 years 4 months ago #62543

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

Has anyone seen this while trying to install using
~/Projects/kstars-on-osx-craft/build-kstars.sh 
-- Build files have been written to: /Users/x/AstroRoot/craft-root/build/libs/cfitsio/work/build
executing command: "/Users/x/AstroRoot/craft-root/dev-utils/bin/ninja" 
[1/90] Building C object CMakeFiles/cfitsio.dir/drvrsmem.c.o
[2/90] Building C object CMakeFiles/cfitsio.dir/drvrgsiftp.c.o
[3/90] Building C object CMakeFiles/Fitscopy.dir/fitscopy.c.o
[4/90] Building C object CMakeFiles/Funpack.dir/funpack.c.o
[5/90] Building C object CMakeFiles/cfitsio.dir/drvrnet.c.o
FAILED: CMakeFiles/cfitsio.dir/drvrnet.c.o 
/Library/Developer/CommandLineTools/usr/bin/clang -DCFITSIO_HAVE_CURL -DHAVE_NET_SERVICES -Dcfitsio_EXPORTS  -fdiagnostics-color=always -O2 -g -DNDEBUG -isysroot /Library/Developer/CommandLineTools/SDKs/MacOSX10.15.sdk -mmacosx-version-min=10.13 -fPIC -MD -MT CMakeFiles/cfitsio.dir/drvrnet.c.o -MF CMakeFiles/cfitsio.dir/drvrnet.c.o.d -o CMakeFiles/cfitsio.dir/drvrnet.c.o   -c /Users/x/AstroRoot/craft-root/build/libs/cfitsio/work/cfitsio/drvrnet.c
/Users/x/AstroRoot/craft-root/build/libs/cfitsio/work/cfitsio/drvrnet.c:313:7: error: implicit declaration of function 'alarm' is invalid in C99 [-Werror,-Wimplicit-function-declaration]
      alarm(0);
      ^
Thanks
3 years 4 months ago #62604

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

  • Posts: 992
  • Thank you received: 155

Replied by Peter Kennett on topic Kstars 3.5.0 OSx

I just tried to use KStars 3.5 for OSX on my Macbok Air (running Catalina). I found that the app seems to work when not connected to anything, and also when logged into my Linux INDI server at the scope VIA WIFI.
But if I try to connect to the INDI server via Ethernet it crashes to the desktop as soon as it starts loading up the drivers.

I wasted two hours last night trying to figure out why. I rebooted everything multiple times. Every-time I try to connect (via Ethernet) it simply kills KStars.

But, if I go back and try again and connect via WIFI - it connects and starts up the INDI drivers on the Linux machine with no immediate issue.

However - even then it was unstable and crashed at random times. I couldn't see a specific cause. I couldn't waste the lively night anymore and skipped using the Mac and just used the Linux machine only.
I may try again later this week and post logs. But it is so frustrating to go from a stable version before to suddenly having troubles with 3.5.
Last edit: 3 years 4 months ago by Peter Kennett.
3 years 4 months ago #62770

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

Yes, that is what we use beta versions for, to find the issues and solve them. It is not guaranteed to be stable yet, that is why it is a beta version. We want you to try it, to test it, to break it, and let us know what breaks and why. Please don't try to rely on a beta version for your main imaging session. We want to make sure everything gets worked out and gets stable before relying on it. 3.5.0 is a major release with a lot of awesome and huge changes. StellarSolver will take the blind solving times from several minutes down to several seconds. We have eliminated temporary files during the image capture, preview, and analysis, so that you computer isn't always saving lots of temp files. We also eliminated temp files for the solving process. We solved the issues with running astrometry.net on different systems, there is now an internal StellarSolver package that will handle it on any operating system with very little configuration needed. Before there were all kinds of issues with python and system configurations and astrometry wouldn't run on windows at all. There are huge changes in this release, so yeah some things will need to be tested, verified, and fixed.

I have been mostly working on getting StellarSolver up and running, so that has been my main focus, rather than any Mac distribution specific issues. I mean I do all my coding on my Mac using the Mac version. That is where I made StellarSolver and have been making all of my changes in KStars, but that is built on my computer to run on my computer. That doesn't guarantee that the distribution version won't have issues. It is hard for me to know whether what works on my computer will work on yours. So that is why we release the beta to get feedback about that.

We will release the 3.5.0 Mac version for real once it is stable and tested. So please test it and let us know what's wrong.
The following user(s) said Thank You: Craig
3 years 4 months ago #62771

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

That being said, we probably should release another beta, since I think we have fixed a bunch of issues since I made the last DMG.
3 years 4 months ago #62772

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

  • Posts: 183
  • Thank you received: 23

Replied by Paul Muller on topic Kstars 3.5.0 OSx

I appear to have a similar "bug" but on the RPi version - the horizon is upside down....

I'll do some more testing.
3 years 4 months ago #63148

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'm definitely seeing regular crashes of Rob's last 3.5.0 build on MacOS 11.0.1. It's a regular occurrence if I click on the Setup/Summary tab in Ekos while I'm in the middle of an imaging job. I have many crash logs.

I'm trying to get the build script to work here so I can provide better debug information, but that still doesn't work. Trying to work through it.
3 years 4 months ago #63169

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

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.

Time to create page: 0.497 seconds