June 2025 - FFmpeg-trac - lists.ffmpeg.org

#11012(avformat:new): APNG decoder incorrectly assumes fcTL chunk must be immediately followed by fdAT or IDAT
by FFmpeg 15 Aug '25

15 Aug '25

#11012: APNG decoder incorrectly assumes fcTL chunk must be immediately followed by fdAT or IDAT ----------------------------------+--------------------------------------- Reporter: tobbez | Type: defect Status: new | Priority: normal Component: avformat | Version: unspecified Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | ----------------------------------+--------------------------------------- The APNG decoder (more specifically `apng_read_packet` in libavformat/apngdec.c) incorrectly assumes an `fcTL` chunk must be ''immediately'' followed by either an `fdAT` or an `IDAT` chunk. In addition, when the `fdAT`/`IDAT` check fails, the input stream is not rewinded to the start of the chunk that follows the `fcTL` chunk, causing misleading log messages: "tag=ware (0x65726177) len=1399809652" in the output below ought to be "tag=tEXt (0x74584574) len=16". An example file can be created using exiftool on an existing APNG file (`exiftool -Software=example apng.png`). This produces a file where the first `fcTL` chunk is followed by a `tEXt` chunk. Such an example will be attached. How to reproduce: {{{ % ffmpeg -i example.png -f null /dev/null ffmpeg version N-115183-g02c032abcd Copyright (c) 2000-2024 the FFmpeg developers built with gcc 13 (13.2.1_p20240503 p15) configuration: libavutil 59. 17.100 / 59. 17.100 libavcodec 61. 5.103 / 61. 5.103 libavformat 61. 3.103 / 61. 3.103 libavdevice 61. 2.100 / 61. 2.100 libavfilter 10. 2.101 / 10. 2.101 libswscale 8. 2.100 / 8. 2.100 libswresample 5. 2.100 / 5. 2.100 [apng @ 0x55841a01a7c0] Could not find codec parameters for stream 0 (Video: apng, none, 64x64): unspecified pixel format Consider increasing the value for the 'analyzeduration' (0) and 'probesize' (5000000) options Input #0, apng, from 'example.png': Duration: N/A, bitrate: N/A Stream #0:0: Video: apng, none, 64x64, 100k tbr, 100k tbn Stream mapping: Stream #0:0 -> #0:0 (apng (native) -> wrapped_avframe (native)) Press [q] to stop, [?] for help [apng @ 0x55841a01a7c0] In-stream tag=ware (0x65726177) len=1399809652 is not implemented. Update your FFmpeg version to the newest one from Git. If the problem still occurs, it means that your file has a feature which has not been implemented. [apng @ 0x55841a01a7c0] If you want to help, upload a sample of this file to https://streams.videolan.org/upload/ and contact the ffmpeg-devel mailing list. (ffmpeg-devel(a)ffmpeg.org) [in#0/apng @ 0x55841a01a500] Error during demuxing: Not yet implemented in FFmpeg, patches welcome Cannot determine format of input 0:0 after EOF [vf#0:0 @ 0x55841a01cb80] Task finished with error code: -1094995529 (Invalid data found when processing input) [vf#0:0 @ 0x55841a01cb80] Terminating thread with return code -1094995529 (Invalid data found when processing input) [vost#0:0/wrapped_avframe @ 0x55841a01cfc0] Could not open encoder before EOF [vost#0:0/wrapped_avframe @ 0x55841a01cfc0] Task finished with error code: -22 (Invalid argument) [vost#0:0/wrapped_avframe @ 0x55841a01cfc0] Terminating thread with return code -22 (Invalid argument) [out#0/null @ 0x55841a01c940] Nothing was written into output file, because at least one of its streams received no packets. frame= 0 fps=0.0 q=0.0 Lsize= 0KiB time=N/A bitrate=N/A speed=N/A Conversion failed! }}} -- Ticket URL: <https://trac.ffmpeg.org/ticket/11012> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 4

#9523(avfilter:new): segment_times splits at I-frames that are not keyframes
by FFmpeg 12 Aug '25

12 Aug '25

#9523: segment_times splits at I-frames that are not keyframes ----------------------------------+-------------------------------------- Reporter: TurboLed | Type: defect Status: new | Priority: normal Component: avfilter | Version: git-master Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | ----------------------------------+-------------------------------------- Summary of the bug: When splitting segments on an MP4 video that contains I-frames that are not keyframes (not IDR frames), the splitting can occur on those I-frames and make the next segment unreadable. How to reproduce: {{{ % ffmpeg -i sample.mp4 -f segment -segment_times 3 -c copy output%03d.mp4 % ffprobe -i output001.mp4 -show_frames [FRAME] media_type=video stream_index=0 key_frame=0 pts=150144 pts_time=3.128000 pkt_dts=151145 pkt_dts_time=3.148854 best_effort_timestamp=150144 best_effort_timestamp_time=3.128000 pkt_duration=1001 pkt_duration_time=0.020854 pkt_pos=48 pkt_size=599189 width=2720 height=1530 pix_fmt=yuv420p sample_aspect_ratio=1:1 pict_type=I coded_picture_number=1 display_picture_number=0 interlaced_frame=0 top_field_first=0 repeat_pict=0 color_range=tv color_space=bt709 color_primaries=bt709 color_transfer=bt709 chroma_location=left [/FRAME] ffmpeg version 2021-11-18-git-85a6b7f7b7-essentials_build-www.gyan.dev }}} -- Ticket URL: <https://trac.ffmpeg.org/ticket/9523> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 23

#11526(avformat:new): cmfv and cmfa not in hls allowed_extensions
by FFmpeg 10 Aug '25

10 Aug '25

#11526: cmfv and cmfa not in hls allowed_extensions ----------------------------------+-------------------------------------- Reporter: gamer191 | Type: defect Status: new | Priority: normal Component: avformat | Version: git-master Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | ----------------------------------+-------------------------------------- Summary of the bug: Cmfv and cmfa are not in ffmpeg's HLS demuxer's list of allowed_extensions. This causes issues when downloading niconico videos using yt-dlp. This can be reproduced with `yt-dlp "https://www.nicovideo.jp/watch/sm44612421" --downloader ffmpeg` (the cmfa issue can be reproduced using `yt-dlp "https://www.nicovideo.jp/watch/sm44612421" --downloader ffmpeg -f bestaudio`). Alternatively, you can create a .m3u8 file containing {{{ #EXTM3U #EXT-X-TARGETDURATION:174 #EXTINF:135, https://example.com/file.cmfv }}} and then run {{{ % ffmpeg -i file.m3u8 ffmpeg version N-118897-gfc44ccd981-20250323 Copyright (c) 2000-2025 the FFmpeg developers built with gcc 14.2.0 (crosstool-NG 1.27.0.18_7458341) configuration: --prefix=/ffbuild/prefix --pkg-config-flags=--static --pkg-config=pkg-config --cross-prefix=x86_64-w64-mingw32- --arch=x86_64 --target-os=mingw32 --enable-gpl --enable-version3 --disable-debug --disable-w32threads --enable-pthreads --enable-iconv --enable-zlib --enable-libfreetype --enable-libfribidi --enable-gmp --enable-libxml2 --enable-lzma --enable-fontconfig --enable-libharfbuzz --enable-libvorbis --enable-opencl --disable-libpulse --enable-libvmaf --disable-libxcb --disable-xlib --enable-amf --enable-libaom --enable-libaribb24 --enable- avisynth --enable-chromaprint --enable-libdav1d --enable-libdavs2 --enable-libdvdread --enable-libdvdnav --disable-libfdk-aac --enable- ffnvcodec --enable-cuda-llvm --enable-frei0r --enable-libgme --enable- libkvazaar --enable-libaribcaption --enable-libass --enable-libbluray --enable-libjxl --enable-libmp3lame --enable-libopus --enable-librist --enable-libssh --enable-libtheora --enable-libvpx --enable-libwebp --enable-libzmq --enable-lv2 --enable-libvpl --enable-openal --enable- libopencore-amrnb --enable-libopencore-amrwb --enable-libopenh264 --enable-libopenjpeg --enable-libopenmpt --enable-librav1e --enable- librubberband --enable-schannel --enable-sdl2 --enable-libsnappy --enable- libsoxr --enable-libsrt --enable-libsvtav1 --enable-libtwolame --enable- libuavs3d --disable-libdrm --enable-vaapi --enable-libvidstab --enable- vulkan --enable-libshaderc --enable-libplacebo --disable-libvvenc --enable-libx264 --enable-libx265 --enable-libxavs2 --enable-libxvid --enable-libzimg --enable-libzvbi --extra-cflags=-DLIBTWOLAME_STATIC --extra-cxxflags= --extra-libs=-lgomp --extra-ldflags=-pthread --extra- ldexeflags= --cc=x86_64-w64-mingw32-gcc --cxx=x86_64-w64-mingw32-g++ --ar=x86_64-w64-mingw32-gcc-ar --ranlib=x86_64-w64-mingw32-gcc-ranlib --nm=x86_64-w64-mingw32-gcc-nm --extra-version=20250323 libavutil 59. 60.100 / 59. 60.100 libavcodec 61. 33.102 / 61. 33.102 libavformat 61. 9.107 / 61. 9.107 libavdevice 61. 4.100 / 61. 4.100 libavfilter 10. 9.100 / 10. 9.100 libswscale 8. 13.103 / 8. 13.103 libswresample 5. 4.100 / 5. 4.100 libpostproc 58. 4.100 / 58. 4.100 [hls @ 00000257b8f1be40] URL https://example.com/file.cmfv is not in allowed_extensions [in#0 @ 00000257b8eb9f40] Error opening input: Invalid data found when processing input Error opening input file C:\Users\REDACTED\file.m3u8. Error opening input files: Invalid data found when processing input }}} Patches should be submitted to the ffmpeg-devel mailing list and not this bug tracker. -- Ticket URL: <https://trac.ffmpeg.org/ticket/11526> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 9

#11640(avfilter:new): Specific combination of timeclamp, fps, and count on showcqt causing crash
by FFmpeg 09 Aug '25

09 Aug '25

#11640: Specific combination of timeclamp, fps, and count on showcqt causing crash --------------------------------------+------------------------------------ Reporter: Aseer Tayeem | Type: defect Status: new | Priority: critical Component: avfilter | Version: 7.1 Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | --------------------------------------+------------------------------------ Summary of the bug: This bug in showcqt of libavfilter causes a whole array of different memory errors causing crashes. I don't know how important this is, since a memory error could do anything, so I put it as critical. This is using valid inputs to showcqt. How to reproduce: {{{ % ffmpeg -f lavfi -i "amovie=test.mp3, showcqt=timeclamp=0.01:fps=15:count=5 [out0]" out.mp4 ffmpeg version n7.1.1 built with gcc 15.1.1 (GCC) 20250425 % ffplay -f lavfi "amovie=test.mp3, showcqt=timeclamp=0.01:fps=15:count=5 [out0]" ffplay version n7.1.1 built with gcc 15.1.1 (GCC) 20250425 }}} I had some complex filtergraph, until I reduced it to this. Removing any of these three will prevent the crash. Works with any input audio, but I don't know if this changes the behavior. Some other quirks: - Keeping fixed timeclamp=0.01 and count=5. At fps=1-16, it crashes with SIGSEGV. At fps=17, it doesn't crash until you terminate it, then it instead has SIGABRT with an error in free(). At fps=18, it doesn't crash. {{{ # at fps=17 free(): invalid next size (normal) fish: Job 1, 'ffmpeg -f lavfi -i "amovie=test…' terminated by signal SIGABRT (Abort) }}} - Keeping fixed fps=15 and count=5. timeclamp=0.002 causes a SIGSEGV only when terminating the program. timeclamp=0.003-0.011 causes an immediate SIGSEGV. timeclamp=0.012 does nothing. - Keeping fixed fps=15 and timeclamp=0.01. count=1-5 causes immediate crashes. count=6 does nothing. - Overall, these ranges start at the minimum values allowed (fps=1, timeclamp=0.002, count=1), and end at fps=18, timeclamp=0.012, count=6. I didn't try using more precision. - Sometimes it would say something about a `corrupted double-linked list`, but only in ffplay. - With some inputs I saw a malloc assertion failure, but only in ffplay {{{ Fatal glibc error: malloc.c:4434 (_int_malloc): assertion failed: (unsigned long) (size) >= (unsigned long) (nb) }}} - In ffplay at fps=17, I got an error like this: {{{ double free or corruption (!prev) 0KB vq= 11KB sq= 0B }}} -- Ticket URL: <https://trac.ffmpeg.org/ticket/11640> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 6

#9693(swscale:new): change of matrix cannot happen on full range
by FFmpeg 09 Aug '25

09 Aug '25

#9693: change of matrix cannot happen on full range ---------------------------------+-------------------------------------- Reporter: Balling | Type: defect Status: new | Priority: important Component: swscale | Version: git-master Keywords: zscale | Blocked By: Blocking: | Reproduced by developer: 1 Analyzed by developer: 0 | ---------------------------------+-------------------------------------- Summary of the bug: I have BT.709 sample that I want to do a jpeg image from, yet because std- complient jpeg is only bt.601 full range and thus the change of matrix must occur it just sees hevc video as bt.601 full range and does a no-op! Does not happen in png (remove gAMA from png). So apparently c523724c693ee031d8b5351aff6232a1f7d86876 was not enough! How to reproduce: {{{ PS C:\Users\xxxx>ffmpeg.exe -i "this one does it.mp4" -frames:v 1 -q:v 1 318281.jpg ffmpeg version N-105504-g04cc7a5548-20220207 Copyright (c) 2000-2022 the FFmpeg developers built with gcc 11.2.0 (crosstool-NG 1.24.0.498_5075e1f) configuration: --prefix=/ffbuild/prefix --pkg-config-flags=--static --pkg-config=pkg-config --cross-prefix=x86_64-w64-mingw32- --arch=x86_64 --target-os=mingw32 --enable-gpl --enable-version3 --disable-debug --enable-shared --disable-static --disable-w32threads --enable-pthreads --enable-iconv --enable-libxml2 --enable-zlib --enable-libfreetype --enable-libfribidi --enable-gmp --enable-lzma --enable-fontconfig --enable-libvorbis --enable-opencl --disable-libpulse --enable-libvmaf --disable-libxcb --disable-xlib --enable-amf --enable-libaom --enable- avisynth --enable-libdav1d --enable-libdavs2 --disable-libfdk-aac --enable-ffnvcodec --enable-cuda-llvm --enable-frei0r --enable-libgme --enable-libass --enable-libbluray --enable-libmp3lame --enable-libopus --enable-librist --enable-libtheora --enable-libvpx --enable-libwebp --enable-lv2 --enable-libmfx --enable-libopencore-amrnb --enable- libopencore-amrwb --enable-libopenh264 --enable-libopenjpeg --enable- libopenmpt --enable-librav1e --enable-librubberband --enable-schannel --enable-sdl2 --enable-libsoxr --enable-libsrt --enable-libsvtav1 --enable-libtwolame --enable-libuavs3d --disable-libdrm --disable-vaapi --enable-libvidstab --enable-vulkan --enable-libshaderc --enable- libplacebo --enable-libx264 --enable-libx265 --enable-libxavs2 --enable- libxvid --enable-libzimg --enable-libzvbi --extra- cflags=-DLIBTWOLAME_STATIC --extra-cxxflags= --extra-ldflags=-pthread --extra-ldexeflags= --extra-libs=-lgomp --extra-version=20220207 libavutil 57. 21.100 / 57. 21.100 libavcodec 59. 20.100 / 59. 20.100 libavformat 59. 17.101 / 59. 17.101 libavdevice 59. 5.100 / 59. 5.100 libavfilter 8. 26.101 / 8. 26.101 libswscale 6. 5.100 / 6. 5.100 libswresample 4. 4.100 / 4. 4.100 libpostproc 56. 4.100 / 56. 4.100 Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'this one does it.mp4': Metadata: major_brand : qt minor_version : 0 compatible_brands: qt creation_time : 2021-07-05T19:03:03.000000Z com.apple.quicktime.description: [{"rParams":"2560000,{1080, 1920}","appRecord":"1","videoIndex":"1","userDevice":"iPhone11,8","userSystem":"14.2"}] com.apple.quicktime.software: {"TEEditor":"1"},{"isFastImport":"0"},{"transType":"2"},{"source":"1"} com.apple.quicktime.copyright: ba465c12a45eb7a886ad4f22aa7710b6 Duration: 00:00:07.03, start: 0.000000, bitrate: 4004 kb/s Stream #0:0[0x1](und): Audio: aac (LC) (mp4a / 0x6134706D), 44100 Hz, stereo, fltp, 132 kb/s (default) Metadata: creation_time : 2021-07-05T19:03:03.000000Z handler_name : Core Media Audio vendor_id : [0][0][0][0] Stream #0:1[0x2](und): Video: hevc (Main) (hvc1 / 0x31637668), yuvj420p(pc, bt709), 720x1280, 3864 kb/s, 29.01 fps, 29 tbr, 600 tbn (default) Metadata: creation_time : 2021-07-05T19:03:03.000000Z handler_name : Core Media Video vendor_id : [0][0][0][0] encoder : HEVC Stream mapping: Stream #0:1 -> #0:0 (hevc (native) -> mjpeg (native)) Press [q] to stop, [?] for help Output #0, image2, to '318281.jpg': Metadata: major_brand : qt minor_version : 0 compatible_brands: qt com.apple.quicktime.copyright: ba465c12a45eb7a886ad4f22aa7710b6 com.apple.quicktime.description: [{"rParams":"2560000,{1080, 1920}","appRecord":"1","videoIndex":"1","userDevice":"iPhone11,8","userSystem":"14.2"}] com.apple.quicktime.software: {"TEEditor":"1"},{"isFastImport":"0"},{"transType":"2"},{"source":"1"} encoder : Lavf59.17.101 Stream #0:0(und): Video: mjpeg, yuvj420p(pc, bt709, progressive), 720x1280, q=2-31, 200 kb/s, 29 fps, 29 tbn (default) Metadata: creation_time : 2021-07-05T19:03:03.000000Z handler_name : Core Media Video vendor_id : [0][0][0][0] encoder : Lavc59.20.100 mjpeg Side data: cpb: bitrate max/min/avg: 0/0/200000 buffer size: 0 vbv_delay: N/A frame= 1 fps=0.0 q=1.0 Lsize=N/A time=00:00:00.03 bitrate=N/A speed=1.13x video:105kB audio:0kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: unknown }}} The sample is here: https://mega.nz/folder/5EMWDDrS#MlG_UA9CHvG633ldHvmnTQ/folder/tQtm0TpB The downupstream issue is here https://github.com/n00mkrad/flowframes/issues/84 zscale is affected too, foring does not work. Patches should be submitted to the ffmpeg-devel mailing list and not this bug tracker. -- Ticket URL: <https://trac.ffmpeg.org/ticket/9693> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 17

#5419(avformat:new): HLS EXT-X-DISCONTINUITY tag is not supported
by FFmpeg 05 Aug '25

05 Aug '25

#5419: HLS EXT-X-DISCONTINUITY tag is not supported -----------------------------------+--------------------------------------- Reporter: xyq204101 | Type: enhancement Status: new | Priority: normal Component: avformat | Version: git-master Keywords: hls | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -----------------------------------+--------------------------------------- Summary of the bug: I'm trying to read input from HLS and output to RTMP, this works fine if the HLS segments are all in one time sequence. However if the time changes e.g. segments generated from two video files, ffmpeg got error 'Non- monotonous DTS in output stream 0:1;'. According to the HLS documentation, EXT-X-DISCONTINUITY should be used when time sequence changes. (https://tools.ietf.org/html/draft-pantos- http-live-streaming-13#section-3.4.11) But I still got the same error after I added that tag to the m3u8 file. Look at hls.c file in libavformat, it doesn't handle EXT-X-DISCONTINUITY tag. How to reproduce: {{{ ffmpeg -re -i http://hls-server/playlist.m3u8 -acodec copy -vcodec copy -bsf:a aac_adtstoasc -f flv rtmp://rtmp-server/app }}} -- Ticket URL: <https://trac.ffmpeg.org/ticket/5419> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 35

#11570(avdevice:new): v4l2 1.30 breaks build of 7.1.1
by FFmpeg 05 Aug '25

05 Aug '25

#11570: v4l2 1.30 breaks build of 7.1.1 ----------------------------------+--------------------------------------- Reporter: bbhtt | Type: defect Status: new | Priority: normal Component: avdevice | Version: unspecified Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | ----------------------------------+--------------------------------------- Summary of the bug: 7.1.1 build is broken with v4l2 1.30 {{{ libavdevice/v4l2.c: In function ‘device_open’: libavdevice/v4l2.c:141:17: error: assignment to ‘int (*)(int, long unsigned int, ...)’ from incompatible pointer type ‘int (*)(int, int, ...)’ [-Wincompatible-pointer-types] 141 | s->ioctl_f = prefix ## ioctl; \ | ^ libavdevice/v4l2.c:149:9: note: in expansion of macro ‘SET_WRAPPERS’ 149 | SET_WRAPPERS(v4l2_); | ^~~~~~~~~~~~ In file included from libavdevice/v4l2.c:52: /usr/include/libv4l2.h:67:19: note: ‘v4l2_ioctl’ declared here 67 | LIBV4L_PUBLIC int v4l2_ioctl(int fd, int request, ...); | ^~~~~~~~~~ }}} See the attached file for the full build log. How to reproduce: Build with v4l2 1.30 -- Ticket URL: <https://trac.ffmpeg.org/ticket/11570> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 6

#11403(undetermined:new): Recording with kmsgrab can't be stopped properly
by FFmpeg 04 Aug '25

04 Aug '25

#11403: Recording with kmsgrab can't be stopped properly -------------------------------------+------------------------------------- Reporter: superded | Type: defect Status: new | Priority: normal Component: | Version: undetermined | unspecified Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Recording stops only after several Ctrl+C with muxing error. Tested in tty and wayland. First commit with this bug d119ae2fd82a494d9430ff4d4fc262961a68c598. Log: https://pastebin.com/c5rGYV9k -- Ticket URL: <https://trac.ffmpeg.org/ticket/11403> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 3

#11606(avcodec:new): avcodec/dvbsubenc: Broken dvb_encode_rle8
by FFmpeg 03 Aug '25

03 Aug '25

#11606: avcodec/dvbsubenc: Broken dvb_encode_rle8 ---------------------------------+--------------------------------------- Reporter: pbk | Type: defect Status: new | Priority: normal Component: avcodec | Version: unspecified Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | ---------------------------------+--------------------------------------- The rle8 encoding (256 color table) is corrupted. The end of 8-bit/pixel_code_string shall be 2 zeroes (not one): Current code: *q++ = 0x00; *q++ = 0xf0; Correct code: *q++ = 0x00; *q++ = 0x00; *q++ = 0xf0; -- Ticket URL: <https://trac.ffmpeg.org/ticket/11606> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 4

#10966(undetermined:new): Regression - Memory leak when muxing raw h264 streams
by FFmpeg 02 Aug '25

02 Aug '25

#10966: Regression - Memory leak when muxing raw h264 streams -------------------------------------+------------------------------------- Reporter: Francesco | Type: defect Bucciantini | Status: new | Priority: normal Component: | Version: git- undetermined | master Keywords: h264 | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Summary of the bug: When raw h264 streams (i.e raw_video.h264 files) are being muxed in a container, FFMpeg keeps allocating RAM with no clear progress until it goes into paging files on Windows or swap on Linux and then eventually crashes. How to reproduce: Step 1) Create a simple Colorbars script with Avisynth and call it "AVS Script.avs" {{{ ColorBars(1920, 1080, pixel_type="YUV422P16") }}} Step 2) Encode the colorbars with x264 to create a raw_video.h264 stream {{{ x264-10b.exe "AVS Script.avs" --preset medium --profile high422 --level 4.1 --opencl --keyint 1 --no-cabac --avcintra 100 --avcintra-flavor panasonic --deblock -1:-1 --tff --overscan show --colormatrix bt709 --range tv --log-level info --thread-input --transfer bt709 --colorprim bt709 --videoformat component --nal-hrd cbr --output-depth 10 --output-csp i422 --output "raw_video.h264" }}} Step 3) Mux the newly produced raw_video.h264 into any container you like, be it mkv or mxf or whatever {{{ ffmpeg.exe -hide_banner -i "raw_video.h264" -map 0:0 -c:v copy -f mxf "output.mxf" }}} Expected behavior: FFMpeg muxes the file in mxf or whatever container you pick. Actual behavior: FFMpeg keeps allocating RAM until it crashes with no clear progress. In the following example, I'm trying to use the newly encoded H264 stream and the audio from Avisynth on a real file to then re-encode the audio in PCM 24bit 48000Hz little endian and mux the whole thing in mxf [[Image(https://i.imgur.com/NJGfFUV.png)]] [[Image(https://i.imgur.com/jTPU3OZ.png)]] [[Image(https://i.imgur.com/LjoFkkQ.png)]] That's the latest master from today, namely N-114842-g639013aafc from the 17th of April 2024. Using version N-97504-g1128aa8 from 2020 works instead with the exact same commands, which points to a regression. -- Ticket URL: <https://trac.ffmpeg.org/ticket/10966> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 1