I experience Kstars/Ekos freezing on large image sequences. I am using the latest INDI Kstars/Ekos available on Astroberry as of today (2021-11-12).
My camera is a ZWO ASI294mc pro. For testing puposes I defined an imaging sequence of 500 frames (1s exposure). At frame 480 the sequence number does not get increased anymore and the frame "test_Light_480.fits" gets overwritten until the 500 frames are finished (can be seen by the timestamp of the file). When this starts, the following messages start appearing:

Found one coordinate representation.
Found one coordinate representation.
Found one coordinate representation.

(kstars:3450): GStreamer-CRITICAL **: 11:14:17.334: gst_poll_get_read_gpollfd: assertion 'set != NULL' failed

(kstars:3450): GStreamer-CRITICAL **: 11:14:17.334: gst_poll_get_read_gpollfd: assertion 'set != NULL' failed
Found one coordinate representation.

(kstars:3450): GStreamer-CRITICAL **: 11:14:25.592: gst_poll_get_read_gpollfd: assertion 'set != NULL' failed

(kstars:3450): GStreamer-CRITICAL **: 11:14:25.595: gst_poll_get_read_gpollfd: assertion 'set != NULL' failed

(kstars:3450): GStreamer-CRITICAL **: 11:14:25.596: gst_poll_get_read_gpollfd: assertion 'set != NULL' failed
Found one coordinate representation.

The "Found one ..." appears with every frame, but now GStreamer starts complaining. How does gstreamer fit into this? I thought the INDI driver would be talking to the ZWO library and the INDI protocol to Ekos.

Finally, when I close the FITS Viewer after the sequence has finished and I trigger another image capture, the same GStreamer messages will appear, the FITS Viewer window will pop up, but freeze and stay white. The whole Kstars/Ekos needs to be killed now.

This does not happen when using a camera with a smaller sensor (ASI 224mc, 1Mpix instead of 11). And I can also not reproduce this on my Laptop (Ubuntu 20.04 LTS, x64). It looks a bit like a memory issue, but Kstars uses 15% according to top (on a Pi4 with 4GB) and the filesystem also had plenty of space left.

I managed to compile Kstars from GIT yesterday (3.5.6 stable) and it shows exactly the same behavior.

Any suggestions on what to test to narrow down the issue?

Regards + CS
Guido

Read More...