Greetings!

KStars/Ekos has been crashy on my Pi 4 and I have been trying to track down the cause. I do not have hard evidence (yet), but I suspect that the FITS Viewer may be at least partially to blame. When I disable the FITS Viewer, things seem to run much more reliably (though not all crashes are solved).

The two conditions that seem to trigger crashes with the FITS Viewer are when I zoom in significantly, and lots of images coming in quickly. Taking flats fits into the second category. In order to combat this, I run with the "Use FITS Viewer" option unchecked.

---

The point of this thread is that when I take images with "Flat" selected for the Type in Ekos:

• Ekos displays all flat images in the KStars FITS Viewer despite the "Use FITS Viewer" setting being unchecked
  • This includes the initial calibration images taken to determine the flat duration, as well as the actual final flats
• The "Use FITS Viewer" setting checkbox is automatically changed to checked by the application

I have attached a screen recording demonstrating the behaviour so you can see what it looks like / how to reproduce it. The short version is: queue up some "Flat" shots; ensure "Use FITS Viewer" is unchecked; start the capture process; get an unwanted KStars FITS Viewer pop-up; re-open the config window to see that "Use FITS Viewer" is now checked.

I presume this is not expected behaviour, but before I log an issue I want to make sure I've covered all my bases. I don't *think* that I'm missing any settings in any other areas that might affect this, but there are a lot of settings, and they are all in different places.

Is the software doing the wrong thing, or am I just doing something silly?

---

I have experienced this behaviour both in the KStars version released with Astroberry (whatever the latest build was in December/January just gone), as well as KStars compiled from source as of a few days ago (which I am using to attempt to track down the root cause of these issues).

Not that it should matter, but for what it's worth, the images in question are large (8288x5644 @ 16 bit mono), but I do also have a Raspberry Pi 4 with 8GB of memory and a 128GB high-speed SD card, so it's barely making a dent in terms of the throughput and capacity that I have available.

Thanks in advance!

---

Hardware

• Raspberry Pi 4
  • 8GB Memory
  • 128GB High Speed SD Card
• ZWO ASI294MM Pro CCD (Imaging)
• ZWO ASI120MM-Mini CCD (Guiding)
• HEQ5 Pro Mount (using EQMod Driver)
• ZBlox GPS Dongle (using GPSD Driver)

Software
phd2@master (cd1d6a8e / 2021-02-19 17:16:21 -0500)
stellarsolver@master (820befc / 2021-02-13 17:05:49 -0500)
indi@master (4c3f1c60 / 2021-02-28 17:48:55 +0300)
indi-3rdparty@master (4d4b6f4 / 2021-03-02 10:41:28 +0300)
kstars@master (4194cd472 / 2021-03-01 14:41:22 +0300)

Read More...