XnView Software

XnView: MP 0.97.1 - 64-bit
OS: Windows 10 - 64-bit

Effect: XnView crashes (bug report window does not open)

XnView crashes either when lots of images are opened in multiple folders that each contain many images, or when images are rapidly opened in a single folder that cotains many images (usually 2000+ images). Because ntdll.dll is the faulting module with an error code of 0xc0000374 (according to Windows 10), I think it might be a heap corruption issue.

To reproduce:
1. Open an image (any format, larger images are more likely to crash)
2. Continually open more images, spread across different folders
OR
1. Open an image
2. Rapidly open more images in the same folder
Actual behaviour (bug): XnView crashes

Expected behaviour: No crash, images are displayed.



Something worth noting, on Windows 10's Reliability Monitor found in the Control Panel, there is a description on XnView MP's crash, particularly what dll was at fault and its error code. I'll paste the results from a recent crash underneath as I think it might be helpful:

Faulting application name: xnviewmp.exe, version: 0.97.1.0, time stamp: 0x5f856890
Faulting module name: ntdll.dll, version: 10.0.20257.1, time stamp: 0x12a774b2
Exception code: 0xc0000374
Fault offset: 0x0000000000106489
Faulting process id: 0xa54
Faulting application start time: 0x01d6bde280e38989
Faulting application path: C:\Program Files\XnViewMP\xnviewmp.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: 72995992-2bc6-4a6e-a72d-2d1ac300e7b7
Faulting package full name:
Faulting package-relative application ID:

do you have sent the crash report?

Here's a download link to a few recent crash dumps: https://drive.google.com/file/d/1qpe6no ... sp=sharing

woot000 wrote: Sat Nov 21, 2020 3:01 am Here's a download link to a few recent crash dumps: https://drive.google.com/file/d/1qpe6no ... sp=sharing

I have a problem, could you send it with crash uploader?

I can't seem to get the crash uploader to open, double clicking on KCrashReporter_x64.exe doesn't open a window. Is there a way to manually open the crash reporter through XnView?

Here is another crash dump, if you are able to access it: https://drive.google.com/file/d/1EYSjS9 ... sp=sharing

... from version 97.1, many time when opening a folder, Xnviewmp close without any info !!! No crash report !
Thanks

woot000 wrote: Tue Nov 24, 2020 7:01 am I can't seem to get the crash uploader to open, double clicking on KCrashReporter_x64.exe doesn't open a window. Is there a way to manually open the crash reporter through XnView?

Not possible

Here is another crash dump, if you are able to access it: https://drive.google.com/file/d/1EYSjS9 ... sp=sharing

it seems that the crash occurs in jpeg loading

Did some more testing of this bug with version 0.98.0, and this crash is still present, with the crash reporter not opening when this happens.

This crash only seems to occur when opening JPG files for some reason, as I've tested it with both PNGs and GIFs and they don't cause a crash to happen.

are you able to see on which file it crashs when creating thumbnail?

I can see the last image I opened when the program crashes, if that's what you mean.

woot000 wrote: Sat Dec 19, 2020 8:14 pm I can see the last image I opened when the program crashes, if that's what you mean.

Do you have tried the 0.98.0?

I've tried 0.98.0, and the program still crashes as it did, with the program not opening the crash reporter at the end and the same error code from the Windows reliability monitor. I'm still not sure why or how this happens.

I do notice, however, that before it crashes, the program uses a large amount of CPU and RAM, and it appears that it is constantly allocating more and more RAM (image shows CPU and RAM usage with a time difference of one minute)
Here's another crash dump from Windows for 0.98.0: https://drive.google.com/file/d/1MZoH-i ... sp=sharing

An update on the situation: I had the same crash happen to me on version 0.98.1 (64-bit) yesterday, though reproducing it is proving difficult. What I could reproduce however (which I think is related to the same crash) was the high CPU usage I posted about earlier.

If XnView MP has an image open in a folder with a lot of images, and an image is added or removed to that folder via File Explorer (not through XnView MP), the CPU usage increases significantly, often using up as much CPU power as possible. This behavior seems to last longer when the folder has a higher number of images in it.

woot000 wrote: Mon Feb 01, 2021 5:10 am If XnView MP has an image open in a folder with a lot of images, and an image is added or removed to that folder via File Explorer (not through XnView MP), the CPU usage increases significantly, often using up as much CPU power as possible. This behavior seems to last longer when the folder has a higher number of images in it.

How many files do you have in this folder?

The high CPU usage thing (which I found out can also take place when a file is replaced) happens on any folder, but it crashed when it was occurring while XnView MP had many tabs open in a folder with about 30,000 files in it.