Pavel <[email protected]> added the comment: In windows it reads way after the buffer end: Unhandled exception at 0x10251115 (avcodec-52.dll) in ffmpeg.exe: 0xC0000005: Access violation reading location 0x00d3a000. at this point s->gb.buffer_end is: 0x00d38ed4 as you see, it went too far away from the buffer end (4384 bytes), it tried to cross page boundary and that caused access violation.
So, I decided to check what's going on differently on linux box and I got quite surprising results. I added some test code (see attached MJPEG_CRASH.diff) and I got quite surprising results: mjpeg reader on linux reads !!40236!! bytes past the buffer end!! Quite remarkable. Stuff like that definitely causes access violation on windows, I have no idea who something like that doesn't coredump ffmpeg on linux. ________________________________________________ FFmpeg issue tracker <[email protected]> <https://roundup.ffmpeg.org/issue2117> ________________________________________________
MJPEG_CRASH.diff
Description: Binary data
