1.91.6 : Halt upon exiting

Bugs found in XnView Classic. Please report only one bug per topic!

Moderators: helmut, XnTriq, xnview

GMB

1.91.6 : Halt upon exiting

Post by GMB »

Windows XP SP2

Everytime Xnview closes it seems to halt and I need to force quit the app through Task Manager. Doesn't seem to matter what type of media or image I open. It's really strange.

Any ideas?
User avatar
helmut
Posts: 8704
Joined: Sun Oct 12, 2003 6:47 pm
Location: Frankfurt, Germany

Post by helmut »

When closing XnView, it stores the program settings. By default, these are stored in a file named "xnview.ini". No clue why this is so slow on your computer.

In order to track down the problem please try:
1. In Tools > Options, category "System integration", set the option "Save options" to "in registry". (XnView will use the Windows registry for saving it's options, then).
2. Then exit XnView, restart it and exit, again, to see whether it's faster.
GMB

Post by GMB »

Thanks for the response. I've tried your fix but it doesn't seem to fix the problem.
User avatar
helmut
Posts: 8704
Joined: Sun Oct 12, 2003 6:47 pm
Location: Frankfurt, Germany

Post by helmut »

GMB wrote:Thanks for the response. I've tried your fix but it doesn't seem to fix the problem.
Thank you for checking and your reply. If saving the settings is not the problem I have no clue what else could slow down the exiting of XnView.
GMB

Post by GMB »

I've tried re-installing it and I've found a problem. The installer errors when copying XnviewShellExt.dll. Could that be the problem? An old DLL?
GMB

Post by GMB »

OK. I've fixed it. I uninstalled Xnview then removed all the leftover entries to Xnview in the registry, rebooted and then installed it again. Now it's back to it's perfect old self.

Thanks! I love Xnview.
User avatar
helmut
Posts: 8704
Joined: Sun Oct 12, 2003 6:47 pm
Location: Frankfurt, Germany

Post by helmut »

GMB wrote:OK. I've fixed it. I uninstalled Xnview then removed all the leftover entries to Xnview in the registry, rebooted and then installed it again. Now it's back to it's perfect old self.

Thanks! I love Xnview.
Strange. Good that you got this fixed. :-)
GMB

Post by GMB »

It's happening again. It's really strange. Any suggestions? Is this problem happening for anyone else?
User avatar
Clo
XnThusiast
Posts: 4441
Joined: Sun Oct 17, 2004 4:57 am
Location: Bordeaux, France
Contact:

Some clues---

Post by Clo »

:arrow: GMB

:) Hello !

• That doesn't occur here under Win XP-Pro SP1… but :
1. In which mode does the closure fail ? View ? Browser ?

2. Is it a (very) big image displayed when you ask to close ?

3. If you are using the cache, please try to optimize it :
- Options (F12) >> Browser >> Thumbnails >> {Cache tab} [Optimize button].

4. If it doesn't help, please try to close all open images (i.e. from their tabs) and attempt to quit from an empty View window…

Note : Here I use all setting-files in the folder of the programme…

:mrgreen: KR
Claude
Clo
Last edited by Clo on Mon Dec 17, 2007 8:32 am, edited 1 time in total.
Old user ON SELECTIVE STRIKE till further notice
Guest

Post by Guest »

Hi Claude,

Thank you for the help! It is a really strange problem.

1. It looks like it fails in both. View and Browser. I can reproduce the fault in the browser more than the viewer.

2. I cant seem to find a pattern to which type of file, or size of file. I have some images which are over 30,000 px wide 17,000 px high which will close fine one day, and then halt on other days. Very strange.

3. Optimise button. It didn't seem to make a difference.

4. Quitting from an empty view doesn't seem to make a difference either.

Interestingly, one of our other computers with XNview is doing the same thing. Very strange.
User avatar
Clo
XnThusiast
Posts: 4441
Joined: Sun Oct 17, 2004 4:57 am
Location: Bordeaux, France
Contact:

GDI ?

Post by Clo »

:arrow: Guest

:) Hello !

• Since that occurs only in two computers, we could think that any item -external to XnView - could act
and then attempt to discover it…
- Please, try that follows :
- a. Press Ctrl+Alt+Del to get the Win Task Manager,
- b. Add the column “GDI Objects” from its View (or Show ?) menu >> Select columns (not set by default).
- c. Look at this column how many GDI objects are set while XnView is running.
• The goal is to compare the counts when the closure succeeds and when it takes ages…
Hence, you have to keep the Task Manager open.
- If you can notice these two values (having a big meaningful difference with the same image
or with nothing displayed in the two cases), please report them here, that could be useful for the Author…

:mrgreen: KR
Claude
Clo
Old user ON SELECTIVE STRIKE till further notice
User avatar
xnview
Author of XnView
Posts: 46236
Joined: Mon Oct 13, 2003 7:31 am
Location: France
Contact:

Post by xnview »

Anonymous wrote:Hi Claude,

Thank you for the help! It is a really strange problem.

1. It looks like it fails in both. View and Browser. I can reproduce the fault in the browser more than the viewer.

2. I cant seem to find a pattern to which type of file, or size of file. I have some images which are over 30,000 px wide 17,000 px high which will close fine one day, and then halt on other days. Very strange.

3. Optimise button. It didn't seem to make a difference.

4. Quitting from an empty view doesn't seem to make a difference either.

Interestingly, one of our other computers with XNview is doing the same thing. Very strange.
XnView process doesn't quit? Even if you start xnview and quit?
Pierre.
Eblis

Post by Eblis »

Hi,

Sorry to barge in on this thread as well but could the issue be the background loading of thumbnails, the one i mentioned here ?
User avatar
xnview
Author of XnView
Posts: 46236
Joined: Mon Oct 13, 2003 7:31 am
Location: France
Contact:

Post by xnview »

Eblis wrote:Hi,

Sorry to barge in on this thread as well but could the issue be the background loading of thumbnails, the one i mentioned here ?
Please send me your email by PM (i would like to send test version)
Pierre.
GMB
Posts: 4
Joined: Wed Dec 19, 2007 7:25 am

Post by GMB »

It looks like the upgrade to 1.92 has fixed the problem. Thanks Everyone!
Post Reply