XnView Software

This is a weird one. When scrolling down a list of files and folders in XnView MP, I can double-click on a folder to open it. I can also press the main Enter key to do the same thing. But if I press the NumPad Enter key, XnView MP crashes. Every time. Any folder.

Could this be a keyboard scancode that's not being handled correctly?

I'm using Windows 7 Ultimate, 64-bit. Microsoft Natural Ergonomic Keyboard 4000 and IntelliType drivers. ASUS motherboard, Intel Core i7, 16GB, etc. The behavior I'm describing is on an internal, local hard drive. Otherwise, XnView MP works great!

Wups... just noticed the 0.56 update. Installed... but problem persists. NumPad Enter on a folder = crash.

Sorry but i can't reproduce

xnview wrote:Sorry but i can't reproduce

Very strange. I've just updated to version 0.61, still have the same issue. Press the main Enter key on a folder in Browse mode, and it opens the folder. Press the Numpad Enter key, and I get a message from Windows saying that "XnViewMP has stopped working." This is 100% consistent on my system.

Any other use of Numpad Enter in XnViewMP is just fine. For instance, I can press it on a file, and it opens in View mode, no problem at all. But press it with a folder selected, and it's a crash every time.

Hard to even guess at what's happening. I can understand if the keyboard were issuing an invalid scancode, it might not be recognized. But what kind of input could cause XnViewMP to actually crash??

I'm running Windows 7, 64-bit. No special keyboard utilities. Microsoft Natural Ergonomic Keyboard 4000, IntelliType drivers. I'm a touch-typist and a heavy keyboard user, but I've never seen this kind of problem with any other software. For instance, I'm just trying it now in the Browse mode of ACDSee Pro 8.0 (the last version I bothered with), and Numpad Enter works with no problems. Obviously, I can't totally rule out the possibility that there's some hidden problem on my system. But whatever it is, it seems to target only XnViewMP.

XnViewMP works great otherwise... I've encountered no other bugs, and I keep finding more great features.

For what it's worth, here's a Windows error log for the crash event. It does seem to indicate that QtCore4.dll is where the problem is happening. The rest is gibberish to me.

Log Name: Application
Source: Application Error
Date: 7/19/2013 3:57:31 PM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: ZZ-Core-i7
Description:
Faulting application name: xnview.exe, version: 0.52.0.0, time stamp: 0x51e7dddc
Faulting module name: QtCore4.dll, version: 4.8.2.0, time stamp: 0x50ab58b7
Exception code: 0xc0000005
Fault offset: 0x000000000000f5a6
Faulting process id: 0x5390
Faulting application start time: 0x01ce84ba31c2c6cc
Faulting application path: C:\Program Files\XnView\xnview.exe
Faulting module path: C:\Program Files\XnView\QtCore4.dll
Report Id: 71d91760-f0ad-11e2-bf01-0250895f0d01
Event Xml:
<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="2013-07-19T19:57:31.000000000Z" />
<EventRecordID>9942</EventRecordID>
<Channel>Application</Channel>
<Computer>ZZ-Core-i7</Computer>
<Security />
</System>
<EventData>
<Data>xnview.exe</Data>
<Data>0.52.0.0</Data>
<Data>51e7dddc</Data>
<Data>QtCore4.dll</Data>
<Data>4.8.2.0</Data>
<Data>50ab58b7</Data>
<Data>c0000005</Data>
<Data>000000000000f5a6</Data>
<Data>5390</Data>
<Data>01ce84ba31c2c6cc</Data>
<Data>C:\Program Files\XnView\xnview.exe</Data>
<Data>C:\Program Files\XnView\QtCore4.dll</Data>
<Data>71d91760-f0ad-11e2-bf01-0250895f0d01</Data>
</EventData>
</Event>

are you able to reproduce it with a clean .ini?