×

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

Bi-monthly release with minor bug fixes and improvements

Frequent crashes: Exceptions thrown in event handler.

  • Posts: 23
  • Thank you received: 1
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:[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 ....?

File Attachment:

File Name: logs.tar.gz
File Size:1,941 KB
1 year 4 months ago #88380
Attachments:

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

  • Posts: 1221
  • Thank you received: 565
@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.
1 year 4 months ago #88386

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

[2022-11-19T21:41:53.001 PST DEBG ][     org.kde.kstars.ekos.guide] - Less than 10 measurements!

Why is this getting triggered every few milliseconds??
Last edit: 1 year 4 months ago by Jasem Mutlaq.
1 year 4 months ago #88387

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

  • Posts: 23
  • Thank you received: 1
More error messages:

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.
1 year 4 months ago #88445

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

  • Posts: 23
  • Thank you received: 1
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.

File Attachment:

File Name: logs.tar_2...11-30.gz
File Size:11,677 KB

File Attachment:

File Name: logs.tar_2...11-30.gz
File Size:11,677 KB
1 year 4 months ago #88649
Attachments:

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

  • Posts: 1221
  • Thank you received: 565
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
- invent.kde.org/education/kstars/-/merge_requests/791
- invent.kde.org/education/kstars/-/merge_requests/792
Those changes will be part of the next release, which will be up for testing soon.

Not sure if these things are causing your crash, though. Of course, you can also test without dark-guiding enabled.
Hy
The following user(s) said Thank You: Wes Mitchell
1 year 4 months ago #88662

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

  • Posts: 23
  • Thank you received: 1
Thanks, I'll try it out, but not likely for another week; we're in the middle of December rains, which is good for California, but bad for stargazing.

BTW, I did turn off dark guiding, and had a nice run over a few hours, until the seeing got too bad to guide.

I run kstars from command line to accumulate output over lots of runs : $ kstars >>kstars.log 2>&1 &
Last edit: 1 year 4 months ago by Wes Mitchell.
1 year 4 months ago #88790

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

  • Posts: 23
  • Thank you received: 1
Hy,

I was able to run several hours of imaging tonight, with no crashes. I had dark guiding turned on. So I believe your fixes worked!
Thanks
Wes
1 year 4 months ago #88889

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

Time to create page: 0.579 seconds