Post any defects you find in the released or beta versions of the ImageMagick software here. Include the ImageMagick version, OS, and any command-line required to reproduce the problem. Got a patch for a bug? Post it here.
Ideally, IM would give a more informative error message. Perhaps there is a memory allocation problem.
From your filename, I guess there are 21000x28000 pixels. In Q16, this needs 4.7GB memory for the input image, and the same again for the output pixels. There are about 9130 output images, and each has an overhead.
How much memory do you have? Using Q8 will halve the memory usage.
Limiting map and memory will force pixels to disk, at the expense of time. Does that complete?
Another option may be to tile in stages, eg first tile into 10240x10240, then tile each result into 256x256.
How big is the input image in width and height and color depth? Can you provide your input image? You can post to some free hosting service such as dropbox.com and put the URL here. Are you running on a hosted server? What is your RAM capacity?
I'm running on an i7, quad-core, with 16Gigs or RAM.
The image is 21000x28000px @ 8bit (256 colour, PNG8)
If memory is the issue, limiting it to use swap space is fine. This doesn't have to be a speedy operation.
What's Q8? I see Q16 noted in the version string.
I cannot share the image as it's confidential. But perhaps simply generating your own might do the job. It's actually a large PDF converted to PNG.
I cannot share the image as it's confidential. But perhaps simply generating your own might do the job. It's actually a large PDF converted to PNG.
Not really an excuse; you could make a non confidential version and share that. We could make a version but not using your process it could be slightly different.
ImageMagick tracks resource consumption to help manage resource demand. It appears that your image is trying to release one more *file* resource than was acquired. That's a bug. However, we need to reproduce the problem before we can offer a fix. If you could post a URL to an image that produces the problem, we will have a fix within a day or two. We did try to reproduce the problem ourselves but our simple example runs without complaint:
We should have a new release tomorrow. It may take some time before brew updates to the latest release. You can always download and install from source-- but wait until tomorrow for the latest patches to mirror worldwide.