I had the latest stable updates installed a couple of nights ago when I was using stellarmate.
Crashes about every 20 minutes or so. The core files are unreadable, at least by me, no stack trace.
I turned on logging, and also ran kstars from the command line and captured stdout and stderr. I saw several messages with this text:
[quote][2022-11-19T22:13:57.275 PST WARN ][ default] - Qt has caught an exception thrown from an event handler. Throwing
exceptions from an event handler is not supported in Qt.
You must not let any exception whatsoever propagate through Qt code.
If that is not possible, in Qt 5 you must at least reimplement
QCoreApplication::notify() and catch all exceptions there.
[/quote]
[2022-11-19T22:13:57.275 PST WARN ][ default] - Qt has caught an exception thrown from an event handler. Throwing
exceptions from an event handler is not supported in Qt.
You must not let any exception whatsoever propagate through Qt code.
If that is not possible, in Qt 5 you must at least reimplement
QCoreApplication::notify() and catch all exceptions there.
Is there some way I can obtain a build of kstars for stellarmate with debug symbols? Then I could provide more detail. Since it appears to be Qt related, it probably has to do with user interaction, or running under vnc, or …?
@Wes, FYI the KStars release is compiled RelWithDebInfo so it should have debug symbols in the binary.
That said, the Qt and other lower-level libraries may not have those symbols.
A few of these:
qrc:/qml/mount/mountbox.qml:502:17: QML MouseArea: Detected anchors on an item tha
t is managed by a layout. This is undefined behavior; use Layout.alignment instead
.
terminate called after throwing an instance of ‘QUnhandledException’
what(): std::exception
and a couple of these:
terminate called after throwing an instance of ‘std::bad_alloc’
what(): std::bad_alloc
although that may have occurred once when I ran out of disk space on my external drive. Still, that should be handled a bit more gracefully, no?
FITSIO status = 107: tried to move past end of file
ffopen could not interpret primary array header of file:
/media/stellarmate/AEF6-B9DB/Capture/Fireworks/Light/NGC_6946_nofilter_Light_180
_secs_009.fits
FITSIO status = 107: tried to move past end of file
FITSIO status = 107: tried to move past end of file
terminate called after throwing an instance of ‘std::bad_alloc’
what(): std::bad_alloc
I tried running kstars and indiserver under EkosDebugger. But the Alignment panel doesn’t function then; the UI is all disabled. Too bad, I’ve had crashes occur while trying to do alignment.
I have more log files to submit from a few nights’ runs. Tonight, I noticed crashes occurring whenever dark guiding started; at least there was a correlation. Not, of course, every time, but often enough. The Ekos logs show the last line before the crash, while the kstars log shows exceptions, like bad_malloc. logs.tar.gz (11.4 MB) logs.tar.gz (11.4 MB)
Wes, I took a peek at your latest log and saw that it was compiled 11/10/2022
Build: 2022-11-10T19:59:08Z
I did repair some issues with dark guiding after that, based on your previous posts, and committed them about a week ago–particularly the 0-second dark-guiding interval in !791