[FFmpeg-trac] #6375(ffmpeg:reopened): [bug][regression] Too many packets buffered for output stream

[FFmpeg]

#6375: [bug][regression] Too many packets buffered for output stream
------------------------------------+------------------------------------
             Reporter:  p137        |                    Owner:
                 Type:  defect      |                   Status:  reopened
             Priority:  important   |                Component:  ffmpeg
              Version:  git-master  |               Resolution:
             Keywords:  regression  |               Blocked By:
             Blocking:              |  Reproduced by developer:  1
Analyzed by developer:  0           |
------------------------------------+------------------------------------

Comment (by afarah):

 I have a specific video file (below) which ffmpeg from git-master (at
 1193301758b8af2ccd05e0dba5c4320e1e0702ac) fails to process with `Too many
 packets buffered for output stream 0:1`, unless `-max_muxing_queue_size
 9999` is passed as an argument, as reported by NoX (above). The input
 video file was successfully generated using ffmpeg itself (more precisely
 with `ffmpeg -i original.mp4 -ss 01:34:56 -t 00:00:38 -c copy input.mp4`,
 where original.mp4 is a 3GB file, using ffmpeg 3.2.4).

 Full command line to reproduce the error: `ffmpeg -v 9 -loglevel 99 -i
 input.mp4 /tmp/out.mp4`

 [Full output for ffmpeg from git
 master](https://paste.ubuntu.com/25224478/).

 ffmpeg 3.2.4 fails with a different error than the one from git master,
 and passing the aforementioned parameter does not fix the issue. Namely,
 it fails with `Unable to parse option value "-1" as pixel format`.
 [Compile options, full command line and
 output](https://paste.debian.net/plainh/7c7a9177). I can provide more info
 if necessary. Notice that I built ffmpeg from git master on a Debian
 system whereas 3.2.4 was built on Gentoo (I can (re)build both on the same
 system if need be).

 The file is 20MB so [externally
 uploaded](http://inf.ufrgs.br/~afarah/files/ffmpeg_bug_report.mp4), sorry,
 making it shorter "solves" the issue.

--
Ticket URL: <https://trac.ffmpeg.org/ticket/6375#comment:12>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker