100% CPU usage when exiting

[Rotareneg]

When I exit XnView 1.74 the window will close but the program will continue running for a moment while using 100% of available CPU time before terminating. This is on XP Pro SP2, the CPU's a Celeron 1.2 GHz, and it's got 512 megs of RAM.

[helmut]

When I exit XnView 1.74 the window will close but the program will continue running for a moment while using 100% of available CPU time before terminating. This is on XP Pro SP2, the CPU's a Celeron 1.2 GHz, and it's got 512 megs of RAM.

Please have a look at topic Slow starting and quitting (1.70.2 and above).

[ckit]

Try removing all XnView plugins from C:\Program Files\XnView\Plugins and see if that fixes the problem.
If it does, re-install the plugins again.

[Rotareneg]

Setting it to use the registry instead of the .ini file solved the problem, many thanks!

[ckit]

I would like to see XnView use the Registry for settings as a default setting on new installs.
Esp. if it will prevent lock ups and other problems.

[helmut]

I would like to see XnView use the Registry for settings as a default setting on new installs.
Esp. if it will prevent lock ups and other problems.

The problem with slow startup and slow exit seems to occur every now and then. People who do not know XnView well might even think: "Nice application, but way to slow! Takes 10 seconds to start-up!" and we never hear of them.

So I also think that either this issue should be solved (even if it is a Windows problem, it is an XnView problem) or by default the Windows registry should be used.

[xnview]

So I also think that either this issue should be solved (even if it is a Windows problem, it is an XnView problem) or by default the Windows registry should be used.

The problem is windows + virus scan with xnview.ini

[Lostclown]

I would like to see XnView use the Registry for settings as a default setting on new installs.
Esp. if it will prevent lock ups and other problems.

In light of the problems with virus scanners and windows this is a good idea.
Although I prefer using an ini-file for settings myself.

Whether it is XnView's problem or not is irrelevant.
A simple suggestion with a simple solution that solves problems is good Period

A user that would select an option to use an ini file for settings is likely to know something about what he is doing and should be able to change it back if it gives him problems.

Regards, Lostclown

[Dreamer]

I use registry settings, for faster start, but if I change settings I use ini, it's not very simple - I must change option to "use registry to save options" - uchceck it, close xnview, start xnview, change that option again - check it. I've got also another backup of ini file... Why? After Windows (and xnview) reinstall I need my settings - I don't want to set up all settings again and again (and I don't use just xnview )

So I see a solution in automatic saving of registry settings to an ini file (after every change or when xnview exits)

Or button for save settings to an ini file or to a reg file.

[Rotareneg]

Yep, it was NAV's auto-scaning the .ini causing my slowdown. If your AV program supports it you can just exclude that specific file (xnview.ini) and it'll work fine if you don't want to use the registry.