[FFmpeg-trac] #9351(undetermined:open): bug in several windows builds when reencoding h.264 to h.265 with GPU

[FFmpeg]

#9351: bug in several windows builds when reencoding h.264 to h.265 with GPU
-------------------------------------+-------------------------------------
             Reporter:  John Dury    |                    Owner:  Timo R.
                 Type:  defect       |                   Status:  open
             Priority:  normal       |                Component:
                                     |  undetermined
              Version:  unspecified  |               Resolution:
             Keywords:  ffmpeg gpu   |               Blocked By:
  buffer                             |
             Blocking:               |  Reproduced by developer:  0
Analyzed by developer:  0            |
-------------------------------------+-------------------------------------
Comment (by John Dury):

 I tried -extra_hw_frames 5 all the way to 15. They all fail with the same
 error:
 [hevc_nvenc @ 000000c920fbb940] Failed locking bitstream buffer: not
 enough buffer (14): .19x
 video encoding failed: Buffer too small

 Replying to [comment:20 Balling]:
 > Replying to [comment:19 John Dury]:
 > > I tried adding "-extra_hw_frames 5" and it still fails on latest build
 (07/27) of gyan.
 >
 > try 6 and more. Again, that is the bug here, since it beaks after 10th
 (-v debug)
 >
 > [h264 @ 000002b1809d5fc0] nal_unit_type: 1(Coded slice of a non-IDR
 picture), nal_ref_idc: 0
 >
 >
 > BTW, crazy that there is no space there before bracket. See:
 https://github.com/FFmpeg/FFmpeg/blob/870bfe16a12bf09dca3a4ae27ef6f81a2de80c40/libavcodec/h2645_parse.c#L307
 (and line 324).
 >
 > BTW, Failed locking bitstream buffer: not enough buffer (14): happens
 because of Ctrl-C here. Not because of code. Though, IMHO, also a bug.
-- 
Ticket URL: <https://trac.ffmpeg.org/ticket/9351#comment:21>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker