I have had issues with KStars terminating or becoming unresponsive while collecting multiple images. "Use FITS viewer" is checked and it seemed to possibly be somehow related. With ongoing bad weather have not progressed collecting logs to submit a query. I don't know if it is a real issue but have the following after seeing the advise to run KStars in a terminal session.
Oct 18.
kstars-bleeding.x86_64 3.0.0-12.2 @home_lupinix-indi_fedora-bleeding
Found one coordinate representation.
Found one coordinate representation.
pa_write() failed while trying to wake up the mainloop: Bad file descriptor
pa_write() failed while trying to wake up the mainloop: Bad file descriptor
pa_write() failed while trying to wake up the mainloop: Bad file descriptor
KCrash: Application 'kstars' crashing...
KCrash: Attempting to start /usr/libexec/drkonqi from kdeinit
sock_file=/run/user/1000/kdeinit5__0
Warning: connect() failed: : No such file or directory
KCrash: Attempting to start /usr/libexec/drkonqi directly
Invalid read from eventfd: Bad file descriptor
Code should not be reached at pulsecore/fdsem.c:157, function flush(). Aborting.
Unable to start Dr. Konqi
[tg@chai ~]$ org.kde.drkonqi: The specified process does not exist.

Can you reproduce this? If yes, how exactly?

Please updated your signature with your system info + equipment as well.

I’ve had the exact same issue the last couple of times I tried using Stellarmate /Kstars. It occurred two weekends in a row. Stellarmate as server with Kstars/Ekos running on my Windows 10 Surface. Kstars would crash on my surface some random number of captures into a sequence. I had to stay up all night both times continually resetting the sequence. I was running the latest nightly builds on both Stellarmate and my Win 10 Surface. I too feel like the crashing is rested to the FITS viewer. I’ve since swapped back to my M3 compute stick with SGP until Kstars proves to be more stable. Hope the new release is more or less bug free as I love Kstars! I may swap back to Stellarmate my next night out and test with the newest nightly build since it has been a couple of weeks.

There is no pattern at all to this crash? no crash log?

I was trying to do other things and did not take the time to look into why it was happening. Probably not helpful but
I'll attach a log from 3 different nights, I have another 4 that all appear to end in a similar way. I think this indicates a crash or more frequently progress stops and the UI is unresponsive, so they could be a forced kill of KStars.

Is this the Windows version? My Ubuntu KStars works great, but the Windows 10 build crashes with FITS viewer.

Hi,

Has anyone managed to find a fix for this issue? Same as everyone else I am trying to run Kstars on a Surface Pro running Windows 10. Kstars crashes every time an exposure is taken with no error being reported. I have tried using low resources mode and deselecting "use FITS Viewer"

Hi,

Has anyone found a work around for this issue? I am also trying to run Kstars on a Surface Pro running Windows 10. Kstars crashes every time an exposure is taken. I have tried using low resource mode and disabling FITS viewer but so far nothing has worked. There is no error reported when Kstars crashes.

Opening Event Viewer in Windows I can see the following error:

Faulting application name: kstars.exe, version: 0.0.0.0, time stamp: 0x5d1c22fe
Faulting module name: Qt5Core.dll, version: 5.12.4.0, time stamp: 0x5d0a2894
Exception code: 0xc0000005
Fault offset: 0x00000000001be4e5
Faulting process ID: 0x3758
Faulting application start time: 0x01d533a6c8c2570a
Faulting application path: C:\Program Files\KStars Desktop Planetarium\bin\kstars.exe
Faulting module path: C:\Program Files\KStars Desktop Planetarium\bin\Qt5Core.dll
Report ID: 942aa12a-3f5d-4786-a3ca-65e03c1fb01d
Faulting package full name:
Faulting package-relative application ID:

I hope this can help finding the source of the issue

I purchased a Dell just to see if it was Microsoft Surface related, same issue. Crash on fits viewer.

I’m getting same issue but mine is on a Win 7 machine. Twice last night I was imaging. Everything was running smoothly. Set my sequence of 60 x 10 sec exposures. The first time it got through about 7 before crashing. After resetting I started another sequence of the same exposure length and got through 12. No error message except Windows telling me KStars encountered a problem. Oh and I to had the FITS viewer running.

Oh forgot to add. I’m running the latest stable builds.

Can you try the latest nightly? binary-factory.kde.org/job/KStars_Nightl...s-msvc2017_64-cl.exe

See if it still crashes.