Legacy ImageMagick Discussions Archive

Do you have the name for one of the files and the line that corresponds to one of those file inside list.txt so I can try to reproduce this?

You can use `Width` instead of `FontPointsize` to set the desired width of your label.

I don't understand why the CVE claims that they need to be disabled. We don't have support for reading files in the PS2 and the PS3 coders.

Yes it is. This is also stated on our website https://imagemagick.org:

The authoritative ImageMagick web site is https://www.imagemagick.org. The authoritative source code repository is https://github.com/ImageMagick. We maintain a source code mirror at https://gitlab.com/ImageMagick.

Do you have a specific area in image where you want to write the text depending on the size of the image? Can you explain in a bit more detail what you are trying to accomplish?

The amount of memory that you can allocate under a 32 bit process is around 2GB. And you are probably hitting that limit here. The limit for a 64 bit process is much higher.

It appears that I misread your issue. This was not only an issue with layered tiff images. Just pushed a patch to resolve this issue.

This issue is caused because the compression differs per channel in a PSD file. The last known compression of a channel will be used for the compression of that layer. And this happens when the pixels of the image are being read. When we ping an image we don't read the pixels.

The latest Q16 any cpu version.

I completely forgot about this issue. I just tried to reproduce it with your sample images with the latest version and I cannot reproduce your issue: using (MagickImageCollection images = new MagickImageCollection()) { MagickImage redimage = new MagickImage(@"I:\issues\topic34150\ROBN2184.jp2&q...

And what have you tried so far?

Magick.NET is not a control but a library that wraps the functionality of ImageMagick. I have no clue how you are using that inside your application but I would suggest that you would upgrade Magick.NET (if that is possible) to the latest version.

The instance that is returned by `image.GetPixels()` is `IDisposable`. You are leaking memory.

We still include it because it has some tweaks to make it work with ImageMagick and we added OpenCL support.

It might be wiser to inspect the content of the temporary files yourself so you can figure out where it fails. I don't think it is likely that this is caused by an invalid JPEG file.