XnView Software

Most often I convert large files up to 45000x45000, it takes more than a minute and the process does not crash. But those files are RGB, so there is no problem with them.

I don't think the operating system limits nconvert's run time.

After entering a command in PowerShell, there is a delay of 1 minute. After that it crashes.

Latency is the same on my local PC as it is on the production server.

On the server there is a notification from Windows, on the local PC - no.

I'm getting an allert from Windows.

"The program "nconvert.exe" is not working.
A problem has caused the program to stop working. Windows will close the program."

I am using the 64-bit version.

Also tried several versions of nconvert :
v6.56
v7.136

The result is the same

It seems to me that there is some limitation in the number of pixels for CMYK. About 2^29 px. But I don't know where to find information about it.

I experimented with files of this ...

Simplified the command to:

"nconvert.exe -overwrite -out jpeg -o ResultFile.jpeg -keepcspace CMYK_31080x17275.JPG"

Unfortunately, using (or not using) flags "-c" and "-dpi" has no effect on crashes.

Only "-keepcspace", CMYK color space and file resolution are affected.

There are no problems with ...

Command: "nconvert.exe -c 2 -overwrite -out jpeg -o ResultFile.jpeg -dpi 100 -keepcspace CMYK_31080x17275.JPG"

File:
CMYK 8-bit
31080x17275 px
DPI 200
Size 103 MB

OS Windows 10 64-bit

Don`t understand... Why does the nconvert.exe crash with this command?

If I use the same file with a lower ...