I updated when I re-installed Astroberry about 2 weeks ago. Astroberry is still at v 2.0.4 which is the version I have. You say updated recently? To be clear, do you mean sudo apt update etc?

sudo apt update && sudo apt upgrade && sudo apt dist-upgrade

Hi Malcolm thanks for reminder. Just did an update. As you say, quite a number of changes recently so will see if this helps. There is another post in the forum that suggests turning off sound for kstars notifications. This has removed the last warning entries in the log when I get a crash. I do wonder however if the warning was due to kstars crashing and not the cause of the crash.

Yes turn off any sound notification in KStars settings. It will get rid of these warnings. Also you have ASI2600 there is thread with similiar problems. First try disable FITS viewer.

www.indilib.org/forum/stellarmate/8620-z...wo-subs.html?start=0

Yes this topic describes the same problem I have had for the last 2 months. It was raised over a year ago I see and I wonder if the fix is being worked on? I went out tonight after installing latest updates today and it only crashed on the first run. I then managed one or two runs of over 20 frames without crashing and fits viewer on. It would be nice to know if this is being worked on or even if it's thought to be fixed. I can try turning fits viewer off but its essential to check images as they are captured.

Hi

I was having crashes with my setup and switched off the sounds after doing the usual googling. “Unfortunately” I also ran into something about image sizes being a problem so changed my camera setup, it’s a sony a7rii and produces full frame 80mb files. I changed it to aps-c mode which dropped the size to around 34mb. Since doing both these things my random crash rate has dropped quite a bit. Check your memory use - I was finding that kstars was using quite a chunk which a long with my setting up zcache (well it seemed like a good idea..) meant there appeared to be very little left on my 4gb Pi.

I still have crashes when trying to look at star profiles when using my sv305 camera which seems to lock up at times but expect that’s a different problem.

Regards

Nigel

I have a 8 gb Pi 4 with a 32 gb SD card. Just taken 15 darks and watched the CPU and memory usage. When downloading images and updating the fits viewer the CPU peaks around 70% and memory usage peaks at about 1.2 gb or around 2.2gb including cache memory. The mount and dome were not being used so need to look again when next observing. No crash to report which is encouraging.

Try CCDciel - it never crashes, has better UI and same features as Kstars. On top of that, it has couple of nice tools for collimating scope.

In general, I have only one issue left, but everything I had issues with "FITS Viewer" and others are no longer an issue. I can run it over a number of days without a problem.

The issue though is that I can't take Bias shots. Just get the circle of death going around but no images. Wasn't an issue before but I have a temporary fix of taking Darks at the fastest shutter.

The problem I *think* lies within the FITS viewer and EKOS summary screen; basically there are weird memory allocation issues that occur that I've found that cause it to crash. Or at least, that appears to be the common thread.

See my thread here with a lot more debugging info that I tried; basically the only thing I've found that's reasonably consistent is using Kstars remotely to offload the FITS viewer to another box instead of the Pi4. I need to really stress-test this via my Windows box and Ubuntu laptop though just to make sure.

Ah, this has in fact been reported as the case here , but it is rearing its ugly head for me at the moment

Disabling the fits viewer was another of the potential fixes I tried. I really must get into the habit of only changing one thing at a time…

So since disabling sounds, reducing the image size my camera was producing and disabling the fits viewer things have been mostly stable.