XnView Software

Im using Version 2.39 on Win7.

This bug has been reported in 2014, but apparently still persists:
http://newsgroup.xnview.com/viewtopic.php?f=36&t=29824

I tried installing the program without XMP or editing the XnView\AddOn\xmp.dll.
Still everytime i open a Gimp-made png in Xnview, it crashes.
Png images made in Inkscape are not affected.

It does not crash when the same image is on my desktop.
It only crashes when it is inside a folder structure on another partition (:F).

When i open the image by doubleclicking on it from my explorer, its opens in XnView without crashing.

Im attaching a sample.

I've no problem opening your uploaded file using XnView Classic 2.35 installed on my C: partition, with your file in a folder on my D: partition, but I wonder if the XMP data could have been lost when the file was uploaded??

If that could be a possibility, you might upload the file again in a ZIP or other archive, which should ensure that is arrives intact...

cday wrote:If that could be a possibility, you might upload the file again in a ZIP or other archive, which should ensure that is arrives intact...

Here you go

Espermachine wrote:

cday wrote:If that could be a possibility, you might upload the file again in a ZIP or other archive, which should ensure that is arrives intact...

Here you go

Your new file still opens for me as above, and the file size is the same as the previous download so nothing seems to have been lost, you may have to wait for XnTriq the file expert...

Perhaps the path of the image is the reason for the problem: XnView Classic supports short pathnames with ASCII chars, only. Could you please try and move the file to the root folder on drive F:?

helmut wrote:Perhaps the path of the image is the reason for the problem: XnView Classic supports short pathnames with ASCII chars, only. Could you please try and move the file to the root folder on drive F:?

Okay, i put the image in F and it does not crash, when i open the image in XnView.
The image was originally deep in a folder structure with four subfolders and at least one of the foldernames had spaces and underscores.

In the meantime i tried to install XnView V2.04 and i can use it without the crashing.

But that does not explain why it only affects images made with Gimp.

Espermachine wrote:

helmut wrote:Perhaps the path of the image is the reason for the problem: XnView Classic supports short pathnames with ASCII chars, only. Could you please try and move the file to the root folder on drive F:?

Okay, i put the image in F and it does not crash, when i open the image in XnView.
The image was originally deep in a folder structure with four subfolders and at least one of the foldernames had spaces and underscores.

Thanks for verifying and interesting to read that it works once the file is moved to the root folder. So one part of the problem are really the spaces in the foldernames (or other special chars) in the folder name. (Underscore is o.k., btw.).

Espermachine wrote:In the meantime i tried to install XnView V2.04 and i can use it without the crashing.

But that does not explain why it only affects images made with Gimp.

Interesting. Perhaps it has something to do with the embedded metadata; older XnView versions didn't read and display or interpret metadata. This should be investigated more.

I don't have any problems opening Gradient.png either.
The file does not contain any metadata or a color profile.

TweakPNG wrote:

Code: Select all

Chunk | Length | CRC      | Attributes                | Contents
------+--------+----------+---------------------------+----------------------------------------------------------------
IHDR  |     13 | c69676e4 | critical                  | PNG image header: 640×400, 8 bits/sample, truecolor, interlaced
gAMA  |      4 | 0bfc6105 | ancillary, unsafe to copy | file gamma = 0.45455
bKGD  |      6 | a0bda793 | ancillary, unsafe to copy | background color = (255,255,255)
pHYs  |      9 | 009a9c18 | ancillary, safe to copy   | pixel size = 2835×2835 pixels per meter (72.0×72.0 dpi)
tIME  |      7 | 9d44472a | ancillary, unsafe to copy | time of last modification = 20 Nov 2016, 16:10:12 UTC
iTXt  |     29 | 642e6507 | ancillary, safe to copy   | text (international), key=“Comment”: “Created with GIMP”
IDAT  |   8192 | ce24ebab | critical                  | PNG image data
IDAT  |   8192 | 5191baca | critical                  | PNG image data
IDAT  |   8192 | 540c47ef | critical                  | PNG image data
IDAT  |   8192 | c1d270d1 | critical                  | PNG image data
IDAT  |   8192 | cd761d6d | critical                  | PNG image data
IDAT  |   8192 | 8ed13a12 | critical                  | PNG image data
IDAT  |   8192 | 1b6981a5 | critical                  | PNG image data
IDAT  |   8192 | 17a0503c | critical                  | PNG image data
IDAT  |   8192 | fa66f225 | critical                  | PNG image data
IDAT  |   8192 | f07a856b | critical                  | PNG image data
IDAT  |   8192 | 45b33ff2 | critical                  | PNG image data
IDAT  |   8192 | cb3d0844 | critical                  | PNG image data
IDAT  |   8192 | 3d0abd63 | critical                  | PNG image data
IDAT  |   8192 | 329de0f7 | critical                  | PNG image data
IDAT  |   8192 | 48a98318 | critical                  | PNG image data
IDAT  |   8192 | 880cd8f4 | critical                  | PNG image data
IDAT  |   8192 | b88cd8b2 | critical                  | PNG image data
IDAT  |   8192 | e720b281 | critical                  | PNG image data
IDAT  |   8192 | 395bd9da | critical                  | PNG image data
IDAT  |   8192 | bc6dac1a | critical                  | PNG image data
IDAT  |   8192 | 4e437488 | critical                  | PNG image data
IDAT  |   8192 | e4a4c4c8 | critical                  | PNG image data
IDAT  |   1322 | 11c5c22d | critical                  | PNG image data
IEND  |      0 | ae426082 | critical                  | end-of-image marker

This is very unfortunate.

I tried putting a single folder named Pillow Emboss into my root F to see if the nested folder structure was the source of the problem, but it crashed again.

I also noticed that all my folders are write-protected, something i cant remove (i googled it, but the procedure for removing the protection doesnt work).
If i copy my PillowEmboss folder to the desktop, opening an image in that folder crashes XnView, unlike a single image, that is perfectly watchable without XnView crashing.

Espermachine wrote:I tried putting a single folder named Pillow Emboss into my root F to see if the nested folder structure was the source of the problem, but it crashed again.

I also noticed that all my folders are write-protected, something I can't remove (I googled it, but the procedure for removing the protection doesnt work).

You don't have any unusual characters, with foreign accents for example, in the filename, do you? XnView Classic doesn't support Unicode characters, and never will, but XnView MP does...

What kind of drive is your F: drive?

If I copy my PillowEmboss folder to the desktop, opening an image in that folder crashes XnView, unlike a single image, that is perfectly watchable without XnView crashing.

You could possibly put the folder with the GIMP-made file in it into a ZIP and upload it (2MiB max current limit, or if necessary create a smaller test folder that shows the problem) and maybe someone will be able to see something useful...

I cant upload the folders to this site, because these files are not meant to be public.
Its a design for a future blog im working on.

The folder structure goes like this:
Volume F
Bildbearbeitung
__Grmn Img Engineering__
Logo
Pillow Emboss

cday wrote:What kind of drive is your F: drive?

I dont understand the question.
Do you mean manufacturer ?

Samsung HD103UI ATA Device
and
WDC WD5000AAKS-60WWPA0 ATA Device

Not sure which one is F and which one is C.

Update: something weird is going on.

I tried to make a duplicate of my folder structure with a gimp made png-image inside, i could upload for you guys to inspect.
When i openend the image it didnt crash.
When i opened the other images that used to crash the program, everything worked fine. No crashing.

I tried to exclude xcf files from displaying and it did not seem to work at first. Even after restarting XnView.
Now all of a sudden it works, although i changed nothing after that.
XCF files are filtered out and nothing seems to crash anymore.

BUT: as soon as i disable the filtering, it crashes again !

Maybe the problem was that i had two files with the same name but different filetypes (xcf and png) ??

i can't reproduce too, please upload a test folder

xnview wrote:i can't reproduce too, please upload a test folder

Ok, here you go.

Thanks for providing a package with a folder structure and images, Espermachine. I've downloaded the images and extracted the folder structure and images. The folder with the files opened fine in XnView 2.37 using right-click in Windows Explorer and "Open with XnView".
Then, I started to create a deeper and deeper folder structure. Once the complete path of the folder structure was 255 characters long, XnView started crashing at startup. Looks like the command line parameter or the internal path has an overflow.

@Espermachine: What is the length of the complete path to your GIMP files?