N.I.N.A. crashes while capturing images in advanced sequencer
Last night I was capturing first light on a new Sky-Watcher Quattro 250p and after about 30 minutes N.I.N.A. crashed. I noticed that it wasn’t running and restarted the advances sequencing session and it looks like it ran for a couple more hours and then failed with the same error. I’ve enclosed the two log files that indicate the stack trace where the failure occurred.
I’m running Version 2.0 HF1 Beta 005 and the following equipment/software was being utilized:
- ASCOM Platform 6.6 - 6.6.0.3444
- EQMOD ASCOM HEQ5/6
- ZWO ASI533MC Pro w/ Driver Version “1,22”
- Manual Focus
- No guiding
I’ll also enclose the advanced Sequence JSON so that you can see what was running when N.I.N.A. crashed. If I need to downgrade to the non-beta or test and update, just let me know.
– Alan Pimm
Comments (6)
-
repo owner -
reporter <div class="preview-container wiki-content"><!-- loaded via ajax --></div> <div class="mask"></div> </div>
</div> </form>
-
reporter I attached the last FITS file created and the crash dump. Looks like it opens in the ASI FITS viewer and is the same size as the others, so I’m not sure if it’s of value. I lowered the log level to Info as you suggested. Here is the Event Viewer detail for the last crash:
Application: NINA.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.AccessViolationException
at NINA.Image.FileFormat.FITS.CfitsioNative.fits_open_memory(IntPtr ByRef, System.String, IOMODE, IntPtr ByRef, UIntPtr ByRef, UIntPtr ByRef, IntPtr, Int32 ByRef)
at NINA.Image.FileFormat.FITS.FITS+<>c__DisplayClass1_0.<Load>b__0()
at System.Threading.Tasks.Task`1[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].InnerInvoke()
at System.Threading.Tasks.Task.Execute()
at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.Tasks.Task.ExecuteWithThreadLocal(System.Threading.Tasks.Task ByRef)
at System.Threading.Tasks.Task.ExecuteEntry(Boolean)
at System.Threading.ThreadPoolWorkQueue.Dispatch()… and here is the detail for the one before it (The initial failure that I reported above):
Application: NINA.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.AccessViolationException
at NINA.Image.FileFormat.FITS.CfitsioNative.fits_read_pix(IntPtr, DATATYPE, Int32[], Int64, IntPtr, IntPtr, Int32 ByRef, Int32 ByRef)
at NINA.Image.FileFormat.FITS.CfitsioNative.read_pixels[[System.UInt16, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]](IntPtr, Int32, Int32)
at NINA.Image.FileFormat.FITS.CfitsioNative.read_ushort_pixels(IntPtr, BITPIX, Int32, Int32)
at NINA.Image.FileFormat.FITS.FITS+<>c__DisplayClass1_0.<Load>b__0()
at System.Threading.Tasks.Task`1[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].InnerInvoke()
at System.Threading.Tasks.Task.Execute()
at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.Tasks.Task.ExecuteWithThreadLocal(System.Threading.Tasks.Task ByRef)
at System.Threading.Tasks.Task.ExecuteEntry(Boolean)
at System.Threading.ThreadPoolWorkQueue.Dispatch() -
reporter Ok, I couldn’t attach the crash dump, it appears to be too large for Bitbucket even when compressed into .zip format. LMK if there is another way to get it to you if needed.
-
repo owner - changed status to closed
Further guards are added. If the issue persists, please reopen.
-
repo owner - removed version
Removing version: 2.0 Beta (automated comment)
- Log in to comment
Hi,
seems like your log level is set to warning only. To better see what’s going on INFO level is better for typical usage.
It looks like the plate solve follower failed to open the FITS file. Can you attach the last one that was taken?
Furthermore it would be good if you could also attach the event viewer event for the hard crash. You can find how to find it here: https://nighttime-imaging.eu/docs/master/site/troubleshooting/general/#event-viewer
Thanks.