Page 1 of 2

Strange bug, not shutting down

Posted: Thu Apr 19, 2007 5:16 am
by Drahken
To begin with, I can't find any way to intentionally reproduce this bug. It has popped up on it's own several times, but I have no idea why or how. I'm hoping that someone else might notice a similar problem and help me narrow it down.

I'm running 1.9.03 on XP media edition. What happens is that sometimes xnview doesn't shut down. It appears to close, but suddenly some other prog will start erroring on me, and when I go to use task manager to shut it down, I see 4 instances of xnview still running. There should never be more than one instance because that how I have it set in the options, there is never more than one instance visible, and all instances appeared to be closed. Trying to narrow it down: Each time I've noticed the problem, I have recently done several things with xnview. I don't know which, or perhaps some combination of them, could be the culprit (or if it's some other variable, like some other prog that's running at the same time or something). 1) I have opened images triggered from another program (xnews to be specific). The prog saves the image, then tells windows to open it in the default viewer (in this case, xnview). 2) I have had at least 8 such images open at once. 3) I have left xnview open with all those images (but minimized) for a few hours at a time. 4) I have opened some other images from windows explorer (ie, by double clicking them as opposed to opening them from within xnview) while those other images were still opened. 5) I have closed those later images using the ESC key.

I almost always use ESC to close images, but rarely have this problem, so the ESC key alone can't be the culprit.
When I close out xnview, everything appears to close properly. There are no errors or any other signs of problems.
This problem does not occur every time I run through that same scenario, it's pretty random.
The really weird part is that it's always FOUR instances of xnview being shown in the task manager when this problem occurs, no more no less. (Although when xnview is actually running, there's only one instance shown.) How many images I view or open/close seems to have no bearing on it.

Re: Strange bug, not shutting down

Posted: Thu Apr 19, 2007 5:40 am
by xnview
Drahken wrote: The really weird part is that it's always FOUR instances of xnview being shown in the task manager when this problem occurs, no more no less. (Although when xnview is actually running, there's only one instance shown.) How many images I view or open/close seems to have no bearing on it.
Yes, very strange, and if you have not 'only one instance'?

Posted: Thu Apr 19, 2007 6:48 am
by Drahken
If I turn of the only one instance option, than however many instances of xnview I open are how many appear in the task manager (iow, it behaves as it's supposed to).

Posted: Thu Apr 19, 2007 8:40 pm
by XnTriq
Back in February a user reported something similar along these lines:
Pararox ([url=http://newsgroup.xnview.com/viewtopic.php?t=11888]How to fix the exit problem I'm encountering? Help![/url]) wrote:I exit XnView but in the process of windows task manager, it still running a xnview.exe process to eat my memories.

The weirdest thing is if I reopen a xnview window and exit, the process simply added one more same .exe!

Still OK…

Posted: Thu Apr 19, 2007 10:36 pm
by Clo
—> XnTriq

:) Hello !

• I remember the same issue in the thread you quote,
where I wrote that a similar problem with Total Commander was caused by another programme
(probably putting a mess in the memory addresses…), and solved by tracking and overpowering the cheeky soft…

• I tested again at this moment, checking with Process Explorer, all works fine :

- I started XnView 1.90.3 and opened an image into…
- Started Process Explorer…
- Closed directly XnView via the [×] Win button,
- It took ~ ½ second to see that the XnView process had gone, and not any other is there…
- I've “Only one instance” ticked, of course (this is my usual setting).

:mrgreen: FR
Claude
Clo

Posted: Sat May 05, 2007 3:03 pm
by Drahken
Well, I found one cause, don't know if it's the only cause. I use a program called SendToFTP to quickly & easily upload stuff (especially images). With SendToFTP you just right click the file/s you want to upload, choose SendToFTP from the context menu and away you go, it can even be used from the open or save dialogs within another program. However, after watching carefully, I have discovered that doing so from within Xnview causes Xnview to not close properly. This problem doesn't occur with other programs though, so there's some kind of interaction goind on between these 2 programs. You can download SendToFTP from here: http://www.snapfiles.com/get/sendtoftp.html it's freeware.
To reproduce: Install SendToFTP, setup the details for your FTP acct, open xnview, open an image (in viewer mode), go to the open dialog, right click a file and send to FTP, cancel the open dialog, close Xnview, check your task manager. There should still be a copy of xnview displayed there. NOTES: You have to have an image open in Xnview while doing this in order for it to jam up. However, it does not have to be the same image that you are uploading.

Posted: Sun May 06, 2007 8:08 am
by marsh
Hello Drahken,

Perhaps an identical problem occurs when using 'send to floppy disk' function. Was the FTP transfer finshed when you closed program?

1. Open browser.
2. Choose open dialog <ctrl + o>.
3. Select RMB context menu on an image.
4. Send it to floppy disk.
5. While it is being copied, close dialog with cancel button.
6. Close program using 'x' icon. Closing program using <esc> may not be possible while transfer is taking place and the browser is displayed.
7. *Program remains in task manager.

Posted: Sun May 06, 2007 7:19 pm
by Drahken
It makes no difference whether you wait for the transfer to complete or not, I've tried it both ways.


I don't have a floppy drive.

Posted: Sun May 06, 2007 8:30 pm
by XnTriq
Hi marsh :-)

when following your step-by-step instructions, I found another strange behavior:
  1. Start the browser.
  2. Go to the Open... dialog.
  3. Right-click on an image to display the context menu.
  4. Hit the ESC key to make the context menu disappear.
  5. Right-click on a non-image file.
  6. XnView “vanishes” without BSOD or error message.
    The program does not remain in the Task Manager's list of running processes.
_____________________________
Windows 2000 SP4 • XnView v1.90.3

Posted: Sun May 06, 2007 9:09 pm
by marsh
Drahken wrote:It makes no difference whether you wait for the transfer to complete or not, I've tried it both ways.
That makes it even stranger. So far, I'm only seeing problem when closing program before 'send to' is finished (such as a large file directed to the 'my documents' folder).
XnTriq wrote:Hi marsh :-)

when following your step-by-step instructions, I found another strange behavior:
  1. Start the browser.
  2. Go to the Open... dialog.
  3. Right-click on an image to display the context menu.
  4. Hit the ESC key to make the context menu disappear.
  5. Right-click on a non-image file.
  6. XnView “vanishes” without BSOD or error message.
    The program does not remain in the Task Manager's list of running processes.
_____________________________
Windows 2000 SP4 • XnView v1.90.3
I cannot recreate that one using Win2k.

Posted: Mon May 07, 2007 4:41 pm
by Drahken
This bug also occurs when I send an image to qmail (a small prog I use for sending email) as an attachment. Again, it doesn't matter whether or not I wait until it's done sending before closing the dialog & xnview, the very act of using the send to function in windows seems to trigger it. I'm using XP media center SP2.

Posted: Thu May 10, 2007 9:15 pm
by XnTriq
marsh wrote:
XnTriq wrote:Hi marsh :-)

when following your step-by-step instructions, I found another strange behavior:
  1. Start the browser.
  2. Go to the Open... dialog.
  3. Right-click on an image to display the context menu.
  4. Hit the ESC key to make the context menu disappear.
  5. Right-click on a non-image file.
  6. XnView “vanishes” without BSOD or error message.
    The program does not remain in the Task Manager's list of running processes.
_____________________________
Windows 2000 SP4 • XnView v1.90.3
I cannot recreate that one using Win2k.
Unregistering XnViewShellExt.dll stops these “crashes” from occurring.

Posted: Sun May 13, 2007 7:50 pm
by marsh
XnTriq wrote:
marsh wrote:
XnTriq wrote:Hi marsh :-)

when following your step-by-step instructions, I found another strange behavior:
  1. Start the browser.
  2. Go to the Open... dialog.
  3. Right-click on an image to display the context menu.
  4. Hit the ESC key to make the context menu disappear.
  5. Right-click on a non-image file.
  6. XnView “vanishes” without BSOD or error message.
    The program does not remain in the Task Manager's list of running processes.
_____________________________
Windows 2000 SP4 • XnView v1.90.3
I cannot recreate that one using Win2k.
Unregistering XnViewShellExt.dll stops these “crashes” from occurring.
Confirmed.

Posted: Sun May 20, 2007 12:21 am
by nim
regsvr32 /u XnViewShellExt.dll doesn't work for me, regsvr32 can't find the file. ? :U

Posted: Thu Jun 21, 2007 11:38 am
by Tintin
Reviving a somewhat old thread... I have the same problem (first trouble after a few years of use) the process will not terminate on one machine. I have re-installed and tried minimal and full install, removed the .ini files and so on so I am fairly confident that this is a 'clean' machine in that respect.

The process will not terminate if I have popped a menu of many kind (RMB of menu line), if I just open a pic and then close XnView the process is terminated and this is 100% reproducible on this very machine. Machine runs Windows XP pro, Danish version. Btw, the tooltip incantation in Options-Browser-Show tooltip was ser to danish keywords at installation and this prevented the tooltip from showing, so maybe the un-terminated process is a result of the OS language?