Multiple XnView instances (Windows XP)

[caveman]

Hello,

When I have multiple instances of XnView v1.66 open, and I then close them all, I notice it takes a long time before I can open a new instance of XnView. It actually looks like the system is locked up. I went into the task manager (XP) and noted that under "Applications" each instance of XnView go away immediately upon closing each instance of Xnview, but under "Processes" there are still multiple instances of XnView running, and it takes a several seconds for each one to go away. A subsequent instance of XnView will not open until the previous processes have ended. Has anyone noticed a similar problem?

Thanks in advance

[helmut]

... A subsequent instance of XnView will not open until the previous processes have ended. Has anyone noticed a similar problem? ...

I have played around a bit to reproduce your problem and started multiple instances of XnView and closed them, again.
I have noticed that XnView doesn't close until the browser has refresed the thumbnails. So if the browser opens in a directory with many large images or a directory located on a network drive, this might take a while. Perhaps this is the problem you observe.

Could you please unset the option "Browser->Launch Browser at startup", open images and see whether your problem persists?

[caveman]

Per your suggestion I verified that the "Browser->Launch Browser at startup" is indeed unchecked.

I also observed that during this "dead time" the cpu usage is maxed out at 100%, so it's working very hard to do whatever it's doing.

I have an older version of Xnview (v1.12) installed on another machine running Win98 and it does not exhibit this anomaly. After closing multiple instances of Xnview I am able to immediately open new instances. The machine that has the anomaly is running XP

Thanks again for looking at this problem with me.

[xnview]

I also observed that during this "dead time" the cpu usage is maxed out at 100%, so it's working very hard to do whatever it's doing.
I have an older version of Xnview (v1.12) installed on another machine running Win98 and it does not exhibit this anomaly. After closing multiple instances of Xnview I am able to immediately open new instances. The machine that has the anomaly is running XP

Very strange problem. And on your 98 with the v1.66, do you have the same problem?
On the XP, do you have a anti-virus?
Pierre.

[helmut]

...I also observed that during this "dead time" the cpu usage is maxed out at 100%, so it's working very hard to do whatever it's doing. ...

A virus scanner really could be the problem (as Pierre suspects). To verify, terminate/exit the virus scanner and then try starting and exiting XnView, again.
Make sure you activate the virus scanner after this test, again.

[helmut]

Caveman et al,

please have a look at post Slow starting and quitting (1.70.2 and above), this might explain and fix your problem.

Cheers,

Helmut