Legacy ImageMagick Discussions Archive

Magick, I have a PNG Image, which may have some issue. I have been able to load it with IM before. But I have problem in IM7. The ImageMagick loaded it with a error message "Read error at scanline 4294967295; got 4529 bytes, expected 4560. `TIFFFillStrip' @ error/tiff.c/TIFFErrors/572", and ...

it looks like this is the reference problem. You probably called "delete blob" in your ~Texture(), if I remember correctly, ImageMigick doesn't export destructor of Blob object. You may need to call DestroyBlob(Blob*) to release the object.

thank you. look forward to update to the new version.

Magick, I am no familiar with Cairo, my vld tool report there is memory leak in imagemagick-6.8.8\cairo\src\cairo-image-surface.c (181): _cairo_image_surface_create_for_pixman_image. I checked that chunk source code. cairo_surface_t * _cairo_image_surface_create_for_pixman_image (pixman_image_t ...

I use IM directly to process. I did step by step debug yesterday, and pretty sure it called j2k decoder from openjpeg. Originally I have problem with J2K file. After hours debug, I finally found out that my j2k file actually is the jp2, which has box header. IM only check file extension or ImageInfo ...

Same as Jason. I have no problem to process that file with IM 6.8.8, and SOC mark is there.

Magick, Is it possible to add the j2c extension into IM? It basically is j2k. right now, I checked the j2c extension myself, then set ImageInfo->magick to be "J2K". It worked, but if you can add it in IM that will be great. Example file can be found at: https://github.com/bitsgalore/jp2kMagic/blob ...

I did a little bit research on this issue. It looks like Glib will release its memory block at the exit time, which probably after the vld memory check and _crt call. If that is the case, those memory allocated by Glib would be considered as leak. I read into Glib source code, it seems like Valgrind ...

Magick, I experienced a strange memory leak report. I create an empty main method. #include "stdafx.h" #include "magick/MagickCore.h" #include <tchar.h> #include "vld.h" int _tmain(int argc, _TCHAR* argv[]) { return 0; } stdafx.h is empty. vld.h is memory leak detector. when run in the debug mode ...

that is great, thank you. I am looking forward for the new release.

I am using ImageMagick-windows which is 6.8.4, it has commented out the tmpnam and replaced with that strange _snprintf().

it is holiday, don't work this hard Merry Christmas and happy new year. love your work!

Magic, Merry Christmas. again, apologize for multiple topic. Testing file. http://upload.wikimedia.org/wikipedia/commons/6/6b/Bitmap_VS_SVG.svg I run under the windows and can't install any svg delegate. From my understand, ImageMagick will convert the svg to MVG, and draw the image out. I maybe ...

Magik, Sorry for the multiple topics. I thought it will be easier for you to read. here is the testing file http://www.microimages.com/gallery/jp2/CB_TM_QQ432.jp2 I found a problem in Core_jp2 package. When process large jp2 image, jasper library will use disk file to store the color components ...

Magic, I found a small memory leak which is in the jp2.c under the CORE_coders package static Image *ReadJP2Image(const ImageInfo *image_info,ExceptionInfo *exception) { …. //here defined a icc color profile icc_profile=(jas_iccprof_t *) NULL; //then made a copy of color profile which never get rid o ...