Lou <[email protected]> added the comment: Crashes no longer occur and the output is playable with MPlayer, but a slightly different "glibc detected" message will still appear:
*** glibc detected *** ffmpeg: double free or corruption (out): 0x09272330 *** ======= Backtrace: ========= /lib/libc.so.6(+0x6bc31)[0xb7248c31] /lib/libc.so.6(+0x6d488)[0xb724a488] /lib/libc.so.6(cfree+0x6d)[0xb724d53d] /usr/lib/libx264.so.80(x264_lookahead_delete+0xfe)[0xb75b4ace] However this time at the end of the FFmpeg output. I'm not sure which update changed this behavior. With r20915 this "glibc detected" message does not appear with other encoders, and x11grab is not a factor (it may never have been) as the message still shows up with a simpler command: ffmpeg -i input -an -vcodec libx264 -vpre hq -crf 22 -s 228x332 output.mp4 Should this be reopened, should the topic title be updated, and should the priority be changed to normal since a seemingly usable output is created? _____________________________________________________ FFmpeg issue tracker <[email protected]> <https://roundup.ffmpeg.org/roundup/ffmpeg/issue1535> _____________________________________________________
