On Tue, 31 Mar 2015 15:53:36 +0000 (UTC) Carl Eugen Hoyos <ceho...@ag.or.at> wrote:
> Michael Niedermayer <michaelni <at> gmx.at> writes: > > > -static size_t max_alloc_size= INT_MAX; > > +static size_t max_alloc_size= SIZE_MAX; > > What would this fix? Nothing yet, because both AVPacket and AVFrame still use ints for size quantities. > I remember several reports about FFmpeg "leaking" > memory where the users just meant that one of > the libraries allocated more memory than the > user meant is sane, sometimes even using the > magical signs "DOS". > I don't remember a report about 16kx16k being > too small... The 16kx16kx is a separate limitation in av_image_check_size(). (And yes I know someone who tried to read highres images with ffmpeg, and it failed because of this.) > (I really don't care and certainly don't object) > _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
