Thanks you so much! I never understood why I couldn't see my image on the Manager Screen. Now it all makes sense and once the session is started I can just display the Manager screen.

 

Crashed again last night with the fits viewer off. Same as before I find the scope pointing straight up. When I restart Kstars I get the message that a version of Ekos is still running. I am still running 32bit Rasbian so I guess I will try moving to the 64 bit version.

You have to love Linux where changing to a 64 bit kernel requires adding one line to a text file followed by a reboot.

I found that KStars continued to crash for me if the summary screen preview was enabled. i believe it still needs to do same image processing as the FITS viewer to display in the manager window so continues to eat memory over the night.

Looking forward to hearing how enabling the 64bit kernel works since KStars will continue be a 32bit application unless rebuilt as a 64bit one.

I personally build the entire INDI / KStars stack on a 64bit Debian 10. With basic Linux knowledge it's not that complicated. It's more or less copy-pasting the instructions available where the code resides.

Last night everything was OK. When I closed down EKOS this morning Kstars did not crash which is a first for me.
Need a few more nights to be sure but maybe using the 64 bit kernel has helped.

Another full night and no problems. Kstars/EKOS working fine in the morning.

Have the same issue: kstars crashes after several subs but indi keeps work. Kstars 3.5.5. on last atroberry rpi4 8gb. CCD QHY600L. There where no chashes with ToupTek IMX571 (same as ZWO ASI2600MC). Power supply is ok as I have 5V10A for rpi4 and dew heaters (2 by 2A each).  I had to disable FITsViewer and Image Preview and it starts work without crashes. There where no other idea to resolve another way.

I was having the same issue but with a QHY268C. I used to have this issue with the 294MC Pro but it was sporadic, now its after one or two frames. I first disabled debayering and that helped but that also meant that the image coming into the Stellarmate App was also not debayered. I have now enabled debayering again but disabled the fits viewer. Now I see my debayered image on the App and Kstars does not crash.

Rishi, Dmitrii, do you use 32bit versions of the OS? If yes, this is the explanation since big camera frames use too much RAM and 32bit has an upper limit of around 3GB, which is too little if all images are kept in memory.

I am using the 64 bit kernel (arm_64bit=1 in config.txt) but not a full blown 64 bit distro.

As someone else mentioned on the recent crashes I did see it was crashing during debayering.

Do you have a core dump?

Does it automatically dump the core when Kstars crashes or would I need to set it up first.

My Pi only has 4GB so I guess having the 64bit kernel doesn't really help?

Typically, the core dump limit is 0, i.e. cores cannot be dumped. To enable it, call
A 4GB Pi should be sufficient. The problem is that for large cameras you need 2.5-3GB of memory, but not more. A single frame from a large CCD uses ~100MB as FITS plus ~200MB as pixmap. If you have both FITSViewer and the viewer on the summary page, you already need 600MB. Plus focusing, aligning, debayering, ..., I measured the values mentioned before. But there is no (major) memory leak that causes the crashes.