PI not shutting down

[sreilly]

I went to re-calibrate my monitor this afternoon and when it was completed, it had written to the LUT, it couldn't write to the ICC file. It had problems with permissions it reported although this hasn't been a problem in the past. I may have reported this a week or so ago but when I use PI and then close the program if I open Task Manager it shows PI still active under the "Processes" Tab. The error writing to the ICC file reported another program was using the profile. Sure enough PI was still active under processes and when I terminated it the file was written as needed. I am using Windows 7 64 bit fully updated and version PixInsight Core 01.08.03.1123 Ripley (x64).

Thanks,

Steve

[MikeOates]

Steve,

I have this as well and it's not restricted to the current version. I also use Windows 7 64 bit and if you watch the process window, PI will close, but it takes a minute or two.

Mike

[sreilly]

I have been watching this and I can't say with any certainty that I didn't wait after closing PI before starting to calibrate the monitor. But if that is the case the calibration process, using NEC's Spectraview and the Monaco Optix calibration puck, somehow wouldn't release the icc file that PI was using. I had noticed previously that PI wasn't releasing the process but never paid any attention to if it did so later as it hadn't been an issue before.

-Steve

[Juan Conejero]

Hi Steve, Mike,

This is not reproducible on any of our development machines with Windows 7 and 8.1. The PixInsight Core application may take some time to close its interprocess communication (IPC) handles on exit, but never more than a few seconds.

Somebody else has this problem on Windows?

[georg.viehoever]

Yes, i have seen this as well. My Windows system is relatively slow (>6 years old), so this may be one contributing factor.
Georg

[sreilly]

I don't think computer muscle is the issue as mine is fast with plenty of memory and SSD. I know I've seen in a number of times and it was at least minutes if not longer after shutting down.

[msmythers]

Just thought I chime in. On my Windows 7 system PI doesn't release the main process sometimes for 5 or 10 seconds when doing an update and closing. This will almost always cause an error when PI reopens automatically. Simply closing PI and reopening fixes the error. The easiest way to prevent the problem when updating is to not check the restart box on the update and wait 10 or 15 seconds before reopening PI.

This last update of the Ref Doc I decided to turn off my Anti-Virus and leave the reopen box checked. I had no issues. Not definitive but would not be surprised by the anti-virus holding up the process or anything PI is writing when closing. I would not be surprised if it is very random depending on other background processes being checked by the anti-virus at the same time. I have Avast for the anti-virus but have excluded the main PI application folder (c:\Program Files\PixInsight\) from virus checking but not any other folders PI writes to. I trust Juan and crew will provide safe files.

On a clean windows install with minimum program and file clutter I would guess this might never show. Welcome to Windows is how I look at it.



Mike

[sreilly]

I haven't had this happen on updates with auto restart as a data point. In fact I never knew this was happening until I had to look at the Task Manager for an unrelated issue previously. The only time it was a problem was after calibrating my monitor and trying to save the icc profile.

-Steve

[MikeOates]

Juan,

I just did a test to see how long the Pixinsight process would run after closing. It was 28 seconds, I then tried again with antivirus turned off and it was the same time.

This is on a AMD Phenom II X4 965 processor 3.41 GHz (Quad core) with 64bit Windows 7

Mike