I am about to give up with Astroberry as kstars crashes when imaging. I would like to move to Stellar Mate but want to see Astroberry working first. It's a shame as I think it has great potential and advanced in terms of networking and architecture.
I have re-installed Astroberry, changed SD card, changed cables, power supplies and USB cables but still see the same issue. It crashes when imaging with the ZWO ASI 2600MM camera but at various times and isn't predictable. It is most likely to crash when taking the second image. With verbose logging selected for all devices in use, the last entries in the log are warnings:
[2022-04-01T23:26:59.603 BST WARN ][ default] - QObject::startTimer: Timers can only be used with threads started with QThread
[2022-04-01T23:26:59.616 BST WARN ][ default] - QtDBus: cannot relay signals from parent Phonon::AbstractAudioOutput(0x45f3ee8 "") unless they are emitted in the object's thread QThread(0x1269270 ""). Current thread is QThread(0x5c73d58 "").
[2022-04-01T23:26:59.618 BST WARN ][ default] - QtDBus: cannot relay signals from parent QObject(0x45f3ee8 "") unless they are emitted in the object's thread QThread(0x1269270 ""). Current thread is QThread(0x5c73d58 "").
[2022-04-01T23:26:59.627 BST WARN ][ default] - QObject::~QObject: Timers cannot be stopped from another thread
From what I have read, these errors relate to the GUI interface.
Do Zoom meetings happen where user problems can be shared? Is there a central resource of known bugs?
Where do I go from here? Help/advice would be appreciated?
I had a lot of crashes as well, but the latest release available 1 or 2 weeks ago has seen the end of most of my crashes. I had it running for the last 3 days until my camera decided to fail. The camera is an old DSLR 450D. Right at this point in time, I will not be updating until I know there are more added features or products that I really need. Even so, I expect to run a new USB operating system storage device for any updates so I easily revert.
Have you updated recently?
Telskop Service TS80 480mm APO FL53 Glass
Canon 450D DSLR
ASI120MM Guide camera.
TIC Focuser NG
Raspberry Pi 4 8GB with Astroberry
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 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.
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.
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.
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
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.
Last edit: 7 months 3 weeks ago by MH. Reason: Direct link to response, not overall thread