ImageMagick.MagickResourceLimitErrorException

[pottmi]

I am getting this error:

Code: Select all

ImageMagick.MagickResourceLimitErrorException: 'TooManyExceptions (exception processing is suspended) @ error/exception.c/ThrowException/969'

The problem occurs because the 92 page tif has three errors like this on each page:

Code: Select all

{"ASCII value for tag \"Copyright\" does not end in null byte. `TIFFFetchNormalTag' @ warning/tiff.c/TIFFWarnings/1007"}    ImageMagick.MagickException {ImageMagick.MagickCoderWarningException}

The number of warning errors is exceeded so that triggers TooManyExceptions errors.

This tiff is generated by third-party software and I have no control over it.

This feature was added as early as version 7.0.7-22. The body of work around this feature was in response to Google's OSS-fuzz project.

How can I turn off this error due to too many warning messages, yet be notified of more severe errors?

I consider this a bug because I can not read the same .tif files I have been reading for at least a year.

I will be happy to donate $100 to get this fixed. One fix would be to allow me to dynamically set the max number (I would set it really high), or to tell the code to suppress reporting of this warning (preferred).

Here are two related external links:

https://stackoverflow.com/questions/54122317

viewtopic.php?t=33989

[rodlie]

You can suppress warnings.

https://imagemagick.org/script/command- ... .php#quiet

[magick]

Thanks for the problem report. We can reproduce it and will have a patch to fix it in GIT master branch @ https://github.com/ImageMagick/ImageMagick later today. The patch will be available in the beta releases of ImageMagick @ https://www.imagemagick.org/download/beta/ by sometime tomorrow.

[dlemstra]

The patch that was made changes the error into a warning and those are not thrown my Magick.NET as you have read in the link that you posted. Would it be possible to share an image so I can add a unit test to Magick.NET to make sure this stays fixed? I am planning to publish a new release later today that includes that patch.