I’ve had a number of crashes while focusing (might be due to problems identified elsewhere) so was looking in the logs and saw this weird error message L-
[2022-11-25T20:42:52.804 GMT INFO ][ org.kde.kstars.ekos.capture] - "Capturing 60.000-second image..."
[2022-11-25T20:42:52.945 GMT INFO ][ org.kde.kstars.indi] - Sony DSLR Alpha-A7r II (Control) : "[INFO] Starting 60 seconds exposure. "
[2022-11-25T20:43:57.875 GMT INFO ][ org.kde.kstars.indi] - Sony DSLR Alpha-A7r II (Control) : "[INFO] Exposure done, downloading image... "
[2022-11-25T20:43:58.928 GMT INFO ][ org.kde.kstars.indi] - "FITS" file saved to "/home/astroberry/AstroPhoto/SONYA7RII/Light/M33__Light_60_secs_2022-11-25T20-43-58_073.fits"
[2022-11-25T20:43:59.650 GMT CRIT ][ org.kde.kstars.fits] - Debayed memory allocation failure. Required Memory: "102.0 MiB" Available system memory: 1.30541e+09
[2022-11-25T20:43:59.663 GMT INFO ][ org.kde.kstars.ekos.capture] - "Download Time: 0.85 s, New Download Time Estimate: 1.19 s.
Not sure why it’s complaining about lack of memory while saying it’s got plenty. I’ve not actually noticed any problem but then I wouldn’t have been watching the fits viewer that closely.
This is on astroberry so not the latest release others are playing with as it’s stuck on 32bit currently. This is on a 4gb Pi with kstars/ekos/indi/phd2/fits viewer running. Doesn’t appear to run low on memory nor cpu.
Wondering if anyone else had run into this and whether it’s actually a problem?
Last edit: 1 year 4 months ago by Nigel Dunmore. Reason: fix quoting so text shows
I had the same problem with my RPi4 4GB running on 32 bit when I switched from my ASI294MC to a Touptec 571 with significantly more pixels. Often crashed during debayering in the FITS viewer.
Quick solution was to deactivate debayering in the viewer. Then I switched to 64 bit and a RPi4 8GB which solved it completely. I think 64 bit + RPi4 4GB will do as well. Had to build myself, don’t know if there is a 64 bit Astroberry image available now (I don’t have the RPi anymore).
Yes there used to be various problems with the fits viewer but most of these seem to have been either fixed or my switching off sound notifications. I don’t actually see/notice a crash so maybe there’s some intermittent problem. I will turn off auto debayering in the fits setup just in case.
Astroberry is still at 32bit with the update to 64bit being worked on I believe. Silver lining of that cloud is I’m stuck pre-optical train on a reasonably stable build which my constant apt updating cannot mess up