Crash on Debayer

[dhb2206]

Since the new update I've been finding that my first attempt at a debayer will crash PI completely; a wipe out - no error messages, just gone. Second time round it works fine. I'm debayering from a Canon 760d in CR2 format set for RGGB to VNG (I used to get a similar behaviour if I left the pattern dropdown on Auto in the previous version, but just for this camera, the 100d was fine to leave on auto).

Not a prohibitve bug, just slightly irritating when you forget it is coming!

Cheers,

David

[Juan Conejero]

Hi David,

This cannot be reproduced under normal working conditions with any of our test data sets, on any supported platform. Can you please upload (Dropbox or something similar) a data set where this problem can be reproduced? Thank you.

[dhb2206]

I suppose a couple of my raw files ought to do the job. Tell you what I will do as well though, I'll have a bash on my laptop as that also has PI installed. If it happens there then I can say it is either something Canon raw or something PI, but if not it is likely to be the config of that machine.

I'll run a test in the next hour or so and post what happened.

Sample files are here: https://www.dropbox.com/sh/h2aq09iuznn2mrq/AAAd1JSREYuT_z6zj7oKW3uoa?dl=0

[dhb2206]

Huh, typical, ran without a hitch, so I think it may be something to do with my super home pc!

What I have noticed is that I get the process window appear, then you usually get the first 8 files listed as going for processing, when it crashes that doesn't happen - PixInsight just disappears altogether. There are no crash messages, no ghost processes, nothing!

[andyp]

Hi dhb!
I get the same thing with debayer first run! Very odd!  I run SFS -> Calib -> Debayer and for first set always a crash!  Reopen and grab same frames for debayer again and all good! Super wierd!


Andy

[dhb2206]

At least it isn't just me. There is just one machine that this happens on, so I reckon there may be some setting somewhere causing the drop out - more likely to be something Windows than PI I fear.

[nmontec]

I am also having this issue, especially when I put more then 20 files in debayer. Very annoying indeed. I am using the latest PI on Win 10

[Juan Conejero]

I cannot reproduce this problem. Can you please upload a data set where this happens?

[mjunius]

May I chime in, as I have the very same problem?
Debayer only crashes the very first time with fresh ImageCalibration output, all subsequent Debayer runs work perfectly. Data are FITS from an ASI294MC Pro.
I'll try to create a minimal set to reproduce, but that's hard as it only seems to happen with new, not yet processed data.

[mjunius]

Just ran ImageCalibration / Debayer on a new set of 34 lights, no problems. I'll try to reproduce with an older data set.

[mjunius]

Got a crash with new data today, let's see if I am able to come up with a minimal set to reproduce.

[mjunius]

Alas, I'm not able to reproduce the error see above. Removing all the calibrated files, clearing the cache, all subsequent Debayer runs work just fine. :-( Am I missing something?

[dhb2206]

Update: Changed my workflow to move the files to be debayered from one external drive to the destination drive before executing debayer. No more error. I believe this could have something to do with one or t'other drive being in sleep mode in windows 10.

[JST200]

I'm glad it's not just me! Add another one to the list. 

I have a set of process Icons: the first is an Image Calibration, which runs successfully. The second is Debayer, which does what others have said. It starts and then PI just exists. No error, no indication of any sort. I re-start PI and rerun the Debayer process icon and it works.

I haven't done extensive tests, but it happens on different sets of images, all of which are over 30 images. The calibrated files are on an SSD drive and the debayered files are written to the same drive. It happens every time, without fail

The images are from an Altair 183c Pro TEC in .fits format.

If it helps I can upload the image files, the master dark and master flat and process icons to a cloud drive. But I won't until you let me know, because it's over a gigabyte.   

Cheers, Jim

[jeburt3]

It happened to me. Last week DEBAYER crashed and I just restarted windows and it worked after that.

Today it happened again with a new set of FIT files I captured Wednesday night.

I had 98 files the first time. I restarted windows and but it still crashed.

The only processes I used with the files were BLINK and SUBFRAME SELECTOR

I reduced the files to 10 and it still crashed. Each time there were no messages, it just disappeared from the screen.

I could send the 10 files if it would Help

ASI294MC Pro

Sharpcap capture program Ver 3.2.6086.0

PixInsight Ver 01.08.06.1475 Ripley (x64)

Windows 10 OS Build 18362.295