XnView Software

0.51 x64

1. Resize selection size blink 1.1 Use fixed ratio mode, set a ratio different from the file itself, in the sample, set to 8:9 on a 1153x1024(1.13:1) file
1.2 Maximize your selection rectangle
1.3 Move you mouse around after step 1.2, you can observe that the selection size is changing while it should NOT. This is reproducable even you set ratio (for example) 9:8 on 900x1000 file, result size is changing between 900x799 and 900x800, while the result should be EXACTLY 900x800
2. View mode crash
2.1 Associate file extension with XnView
2.2 Make a new directory, put any image file in, then create an 7z part package, larger than 20M or more (the extension name of it is 001)
2.3 Double click the image file you just put in, wait for crash. Seems MP is trying to make thumbnail of the 001 file, that may lead to the crash

3. Big file editing hang/crash
MP sometimes hang/crash when editing big image files (editing means resizing, chop image, etc, but not rename or change format)

In my experience, the x64 version will just keep allocating... and allocating... far beyond the memory actually in the system, until it hits the limit of the page file. While it's swapping like crazy, it can take 15-20 minutes to get task manager open and actually kill the app. But, on the bright side, it's never actually crashed, which would have been preferable to trying to allocate more memory than physically available for one image....

(Wikipedia hosts tons of images over 10,000x10,000 that will jam up the system. The one I tried to open was 25,000x24,000, which old xnview could actually (eventually) open. Not sure why MP's data structures are so much less efficient.)