From: Greg R. <ne...@po...> - 2008-01-17 21:02:52
|
>> libpng was "recently" changed (within the last two years or so) to >> artificially limit the maximum size of images it handles > Over 3-1/2 years ago: > version 1.0.16rc1 and 1.2.6rc1 [August 4, 2004] > Imposed default one million column, one-million row limits on the image > dimensions, and added png_set_user_limits() function to override them. > It doesn't affect the images being discussed here. No, and it doesn't sound like what I was thinking of, but maybe that's just poor memory on my part. (I fixed several security problems in another app around that time, and w*h*d overflow calculations were involved.) > If the application is trying the load the entire image into a single array, then > there might be a system limit coming into play. You're right; it does sound very similar to issues surrounding large-file support several years ago. Is the app's output being redirected from stdout to a file? If so, do the file system, the shell, and the app itself support large files (i.e., compiled with -DLARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 in the latter two cases)? Alternatively, Glenn's suggesting a malloc() or other heap limit, but I don't know what limits exist for that or how to increase them if they do exist. Greg |