×

INDI Library v1.9.8 Released (29 Sep 2022)

Bi-monthly INDI Library released with new drivers and bug fixes.

Kstars crashes

  • Posts: 18
  • Thank you received: 2

Replied by MH on topic Kstars crashes

Ah, this has in fact been reported as the case here , but it is rearing its ugly head for me at the moment
5 months 3 weeks ago #82112

Please Log in or Create an account to join the conversation.

  • Posts: 76
  • Thank you received: 5

Replied by Nigel Dunmore on topic Kstars crashes

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.
5 months 3 weeks ago #82120

Please Log in or Create an account to join the conversation.

  • Posts: 147
  • Thank you received: 10

Replied by David Bennett on topic Kstars crashes

I have the same problem with Bias shots. I logged this as an issue and Jasem advised me to install the latest Kstars but I have already got it installed so waiting for a further reply.
I start off the sequence and whirly gig icon goes around but nothing happens. I find if I stop (the square button) the queue then re-start clicking the play arrow it runs. I used to see a message asking me to confirm the camera was covered. I don't see this now but it seems the software is waiting for a response to continue, at least its an impression I have. As I don't have an automated means of blocking light then a manual intervention is ok but some might want to turn it off.
5 months 3 weeks ago #82122

Please Log in or Create an account to join the conversation.

  • Posts: 16
  • Thank you received: 11

Replied by John Laffoon on topic Kstars crashes

Just out of curiosity did you get Error 50 on your 450D? All of a sudden for me as well, Kstars constantly crashes and my canon 500D has failed and no longer works. My not be anything of significance but this post did catch my attention.
5 months 3 weeks ago #82172

Please Log in or Create an account to join the conversation.

  • Posts: 147
  • Thank you received: 10

Replied by David Bennett on topic Kstars crashes

Pleased to say after disabling the FITS viewer I didn't get any crashes last night. Obviously there is something wrong with this viewer so hopefully this can be fixed.
5 months 3 weeks ago #82194

Please Log in or Create an account to join the conversation.

  • Posts: 113
  • Thank you received: 5

Replied by Malcolm Whinfield on topic Kstars crashes

It has been fixed, it appears you might be using version 3.5.7 of KStars. I recently upgraded to 3.5.8 here the problem disappeared.

Check your version using the about the menu in KStars.
Malcolm
Telskop Service TS80 480mm APO FL53 Glass
Canon 450D DSLR
ASI120MM Guide camera.
HEQ5 Pro
TIC Focuser NG
Raspberry Pi 4 8GB with Astroberry
5 months 3 weeks ago #82198
Attachments:

Please Log in or Create an account to join the conversation.

  • Posts: 18
  • Thank you received: 2

Replied by MH on topic Kstars crashes

I was running this version as well, it still crashed aplenty (may or may not be related).

My particular problem was almost certainly two things in conjunction:
  • Much larger camera files (new camera)
  • Astroberry most people get is a 32-bit OS (and may not even have a 64-bit OS)

The only thing I can guess for me due to the errors I saw while attaching gdb to the Kstars process thread and running until it died was that there were memory allocation errors due to the size of the RAM buffer available - so it would attempt to allocate the RAM necessary to hold the image in the viewer(s) and would have a Very Bad Time. Running completely without the EKOS summary viewer and FITS viewer was fine, but not being able to see your resultant images isn't ideal. Running Kstars to connect to the Pi remotely was okay (disabling the viewers on the Pi side, but leaving enabled on the remote host side), but there are latency issues with those large images that can cause weird hangs as well, though you then happily offload the image rendering to the remote host for the viewer(s) versus the Pi handling that lift.

What I ended up doing was actually shelling out for Stellarmate (both for the fact that it has support staff as well as offering a 64-bit version of the OS) and have had absolutely zero crash problems since then. The memory allocation pattern for the viewer also looks way more reasonable and doesn't have large spikes while rendering the images, as though Kstars has pre-allocated a RAM buffer to use versus "just-in-time" allocation.
5 months 3 weeks ago #82261

Please Log in or Create an account to join the conversation.

  • Posts: 147
  • Thank you received: 10

Replied by David Bennett on topic Kstars crashes

I am on 3.5.8 as well. The workaround for me is to disable the FITS viewer then I don't get the crashing when imaging.
I should say I didn't experience any crashing when I took lots of bias frames with FITS viewer on during the day, only experience frequent crashing when imaging at night whilst attempting observations. When I took the bias frames I had everything connected up just didn't turn the mount or dome on.
It seems crashing only happens with the observing sequence of focusing, aligning, guiding then imaging.
Running Kstars in the debugger and see lots of theses messages:
</oneNumber>
</setNumberVector>
Dispatch command error(-1): INDI: Could not find property CCD_TEMPERATURE in ZWO CCD ASI120MM Mini
<setNumberVector device="ZWO CCD ASI120MM Mini" name="CCD_TEMPERATURE" state="Idle" timeout="60" timestamp="2022-04-08T11:23:03">
<oneNumber name="CCD_TEMPERATURE_VALUE">
Strange but looking at the Indi Tab for the guide camera or selecting it in the imaging TAB , the temperature is being displayed.
5 months 2 weeks ago #82288

Please Log in or Create an account to join the conversation.

  • Posts: 147
  • Thank you received: 10

Replied by David Bennett on topic Kstars crashes

Thanks for the feedback on Stellarmate.
5 months 2 weeks ago #82290

Please Log in or Create an account to join the conversation.

Time to create page: 0.712 seconds