STF Window Disappearing

[twade]

To all,

I have updated to the latest version of PixInsight.  I'm running Windows 7 64-bit.  After opening three to four 230+ MB RGB images at the same time, I open an STF window.  I click on "A" in the STF window for each image.  Sometimes, during the STF processing phase, PixInsight "freezes" momentarily.  It almost looks like a "disabled" screen.  Once the STF finishes, everything is back to normal with the exception of the STF window.  It completely disappears from the PixInsight workspace.  I have to go back to the Process Explorer to make it visible again. 

Has anybody else had this strange behavior?  If so, is it fixable?

Thanks,

Wade

[twade]

To all,

I set the "Maximum module thread priority" from Time Critical to Normal.  This seems to have solved the problem.  Every once in a while, PixInsight turns completely white reporting "Not responding" in the title bar, but always seems to return to normal.  The SFT window turns completely white too sometimes.  It is strange, but they return to normal after completing the task.

Wade

[Cleon_Wells]

Wade

Every once in a while, PixInsight turns completely white reporting "Not responding" in the title bar, but always seems to return to normal.

Yes, while on my _c Dark sub WSigma NoNorm Imageintegration/Calibration quest,  my small Dell Win7 laptop, that had only 2 Gig of memory and working with180 Meg files, exhibited this same behavior. After I maxed out the memory (4 Gig) on the Dell this problem seems to have been eliminated.
Cleon

[twade]

Cleon,

only 2 Gig of memory and working with 180 Meg files, exhibited this same behavior.

With 24 GB of memory, I don't think this is my problem.    I upgraded my desktop computer last year in hopes of it handling the ever increasing workload for another 5 to 10 years.

I'm not quite sure what's causing Windows 7 to briefly think PixInsight is "not responding" or completely going white for a brief second or so.  It's not that big of a deal so far.  The disappearing STF window was a pain, but it is fixed now due to tweaking the thread priority.

Wade