Search found 12 matches
- 2016-01-08T05:55:04-07:00
- Forum: Bugs
- Topic: tiff writeImages fail with JPEG compression converted to grayscale
- Replies: 0
- Views: 9550
tiff writeImages fail with JPEG compression converted to grayscale
Some color-images fail under Magick++ when trying to save them in TIF-format with JPEG compression and converted to grayscale If I remove the img.type()-code, writeImages doesnt fail. Error message: Magick: IO error writing tag data. `TIFFWriteDirectoryTagData' @ error/tiff.c/TIFFErrors/553 ...
- 2014-10-16T00:46:15-07:00
- Forum: Bugs
- Topic: assertion failure blobtoimage
- Replies: 3
- Views: 3929
Re: assertion failure blobtoimage
Great, thanks! Was trying to make a patch myself but I'm not experienced enough (;
- 2014-09-23T05:52:47-07:00
- Forum: Bugs
- Topic: assertion failure blobtoimage
- Replies: 3
- Views: 3929
assertion failure blobtoimage
magick/blob.c:338: BlobToImage: Assertion `image_info != (ImageInfo *) ((void *)0)' failed. Code: Magick::Blob mblob_in; mblob_in.updateNoCopy(data, data_length); std::vector<Magick::Image> images; Magick::readImages(&images, mblob_in); data/data_length is 133562 bytes of a 2-page PDF, but also ...
- 2014-04-10T04:48:49-07:00
- Forum: Bugs
- Topic: magick++ copy-on-write forking
- Replies: 9
- Views: 11189
Re: magick++ copy-on-write forking
My mistake. My first test used 15gb of ram, not 16. I wasn't aware of that fork() requires the same amount of free memory as the entire process is using to clone itself, even though it never use that amount of ram due to copy-on-write. So large processes waste 50% of the ram just in order to execute ...
- 2014-04-10T04:18:00-07:00
- Forum: Bugs
- Topic: magick++ copy-on-write forking
- Replies: 9
- Views: 11189
Re: magick++ copy-on-write forking
Did you try with a PDF-file ? The Magick::Image constructor will fail. If you catch the error message you get: root@n2:/root# ./test test.pdf Magick failed - Magick: Postscript delegate failed `test.pdf': No such file or directory @ error/pdf.c/ReadPDFImage/713 The "no such file" comes from that it ...
- 2014-04-10T03:26:13-07:00
- Forum: Bugs
- Topic: magick++ copy-on-write forking
- Replies: 9
- Views: 11189
Re: magick++ copy-on-write forking
Should be easy to replicate (at least as long as you have 32gb ram). See code below. Ulimit on tested machine is: max locked memory (kbytes, -l) 64 max memory size (kbytes, -m) unlimited virtual memory (kbytes, -v) unlimited Available memory when testing was 28gb MAGICK_*LIMIT variables was set to ...
- 2014-04-10T02:32:04-07:00
- Forum: Bugs
- Topic: magick++ copy-on-write forking
- Replies: 9
- Views: 11189
Re: magick++ copy-on-write forking
I'm using the latest public release 6.8.8-10 on your website. Exporting MAGICK_MEMORY_LIMIT and MAGICK_MAP_LIMIT environment variables to 2GiB did not help. I still get ENOMEM error (and also half size output a few times) I verified the variables with "identify -list resource": File Area Memory Map ...
- 2014-04-09T09:50:47-07:00
- Forum: Bugs
- Topic: magick++ copy-on-write forking
- Replies: 9
- Views: 11189
Re: magick++ copy-on-write forking
What also happens when the process gets close to 16gb memory usage is that a pdf convert succeeds but the output gets incomplete. The output file becomes around half the size of what it should be, and when viewing the image you see it is incorrect. The output file (tif) validates ok with identify ...
- 2014-04-09T07:09:21-07:00
- Forum: Bugs
- Topic: magick++ copy-on-write forking
- Replies: 9
- Views: 11189
magick++ copy-on-write forking
I have a linux server with 32gb ram, a C++-application implementing imagemagick and a PDF-file. If I malloc 16gb of ram when starting the application, imagemagick Magick::Image is unable to convert the pdf-file with ghostscript due to clone() and ENOMEM error. A normal fork would share the memory ...
- 2014-04-09T05:07:00-07:00
- Forum: Bugs
- Topic: assertion failed
- Replies: 2
- Views: 4328
Re: assertion failed
It's caused by
Magick::Blob mblob_out;
writeImages(imgs->begin(), imgs->end(), &mblob_out);
This did not happen with version 6.8.6-4
Magick::Blob mblob_out;
writeImages(imgs->begin(), imgs->end(), &mblob_out);
This did not happen with version 6.8.6-4
- 2014-04-09T03:47:42-07:00
- Forum: Bugs
- Topic: assertion failed
- Replies: 2
- Views: 4328
Re: assertion failed
and I'm using 6.8.8-10 Q16 under x64.
- 2014-04-09T03:47:02-07:00
- Forum: Bugs
- Topic: assertion failed
- Replies: 2
- Views: 4328
assertion failed
When working with Magick++ I suddenly get magick/blob.c:3594: SeekBlob: Assertion `image->blob->type != UndefinedStream' failed I don't know exactly what caused it due to heavy parallellism, but I'm not using SeekBlob directly. Im using Magick::Blob, Magick::readImages, writeImages,Magick::Image ...