https://bugzilla.wikimedia.org/show_bug.cgi?id=24821
Daniel Kinzler changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|
https://bugzilla.wikimedia.org/show_bug.cgi?id=24821
Daniel Kinzler changed:
What|Removed |Added
Keywords||need-review
--- Comment #4 from Danie
https://bugzilla.wikimedia.org/show_bug.cgi?id=24821
--- Comment #3 from Daniel Kinzler 2010-08-17 08:11:26
UTC ---
I wasn't talking about failure because of memory limits, but because of
unsupported variants of tiff - codecs, etc. there's quite a few of those, check
out http://www.libtiff.org/i
https://bugzilla.wikimedia.org/show_bug.cgi?id=24821
--- Comment #2 from Tim Starling 2010-08-17 08:05:50
UTC ---
Actually it won't. We use a different shell memory limit on the image scalers
compared to the main cluster.
--
Configure bugmail: https://bugzilla.wikimedia.org/userprefs.cgi?tab=e
https://bugzilla.wikimedia.org/show_bug.cgi?id=24821
--- Comment #1 from Daniel Kinzler 2010-08-17 07:26:12
UTC ---
I understand the issue, and I'll llook into libtiff for this. However, using
identify has one very important advantage: it will fail just in the cases where
convert/mogrify will fa
https://bugzilla.wikimedia.org/show_bug.cgi?id=24821
Tim Starling changed:
What|Removed |Added
Blocks||23258
--
Configure bugmail: https://bu