Page 1 of 1

2.39+Win10: Dropbox crash when press ENTER to switch browser

Posted: Wed Feb 01, 2017 12:34 am
by ruthan
Hello,
i upgraded Windows 7 to Windows 10 and Xnview 2.39 is crashing, everytime when i trying to switch from Fullscreen picture view mode to browser mode, by pressing ENTER,
initially picture is opened through Windows explorer, next picture or previous picture in view mode is working.

Update: Its Dropbox related, its crashing only for pictures which are in Dropbox folder, or something like that, i have tried other folder with lots of pictures and its not crashing,
but when i quited Dropbox it keep crashing.

I would gladly add some logs.

Error message is Xnview stopped working.

I used older version, but bug was the same as in 2.3.9. Im using Xnview more that 10 years but now its unsuable.

In Windows event log is this:
- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2017-02-01T00:43:09.664981300Z" />
<EventRecordID>10187</EventRecordID>
<Channel>Application</Channel>
<Computer>RuThaNPragl</Computer>
<Security />
</System>
- <EventData>
<Data>xnview.exe</Data>
<Data>2.39.0.0</Data>
<Data>58218879</Data>
<Data>xnview.exe</Data>
<Data>2.39.0.0</Data>
<Data>58218879</Data>
<Data>c0000409</Data>
<Data>0037af8c</Data>
<Data>60ec</Data>
<Data>01d27c2426b4f644</Data>
<Data>C:\Programy\XnView\xnview.exe</Data>
<Data>C:\Programy\XnView\xnview.exe</Data>
<Data>b71cca67-3f5f-4373-8ab7-d9a0fb66b327</Data>
<Data />
<Data />
</EventData>
</Event>

Re: 2.39+Win10: Dropbox crash when press ENTER to switch bro

Posted: Thu Feb 02, 2017 2:34 pm
by xnview
I have no crash on dropbox, do you have the crash for every dropbox folder?
you start XnView, open in fullscreen a photo, press ENTER and crash?

Re: 2.39+Win10: Dropbox crash when press ENTER to switch browser

Posted: Tue Dec 05, 2017 4:12 am
by ruthan
Now it looks like finally fixed, with 2.43