[FFmpeg-trac] #7881(avcodec:new): HEVC encoder crashes including OS on high performance environment

FFmpeg trac at avcodec.org
Sun May 5 19:19:43 EEST 2019


#7881: HEVC encoder crashes including OS on high performance environment
---------------------------------------+-----------------------------------
             Reporter:  Nobody2112     |                    Owner:
                 Type:  defect         |                   Status:  new
             Priority:  normal         |                Component:  avcodec
              Version:  unspecified    |               Resolution:
             Keywords:  libx265 crash  |               Blocked By:
             Blocking:                 |  Reproduced by developer:  0
Analyzed by developer:  0              |
---------------------------------------+-----------------------------------

Comment (by Nobody2112):

 Thanks for the fast response.

 As reported in the initial ticket. The problem is independent of the
 source video file and also the ffmpeg.exe. In my application I use API
 calls for my application not the exe with parameters.

 I have created a API call based test using generated YUV frames and no
 thread functionality from my site, which has no decoding functionality
 included an show the same result.

 The I tried if the problem also occurs using the “EXE” with parameters.
 And it exists also with the exe, but only on very fast systems.

 ffmpeg -f lavfi -i testsrc2=duration=300:rate=25:size=pal -pix_fmt yuv420p
 -c:v libx265 -preset medium -x265-params lossless=1 "w:\testh265.mkv" -b:v
 1M >>w:\log.txt 2>&1

 If I use fullHD (hd1080) it not occurs.

 I’m not able to build FFMpeg by myself. I downloaded the last build from
 Zeranoe (today), for the attached tests. The included x265 part is the
 same I used for my test before.
 Due to the fact, that the complete OS crashes when the error occurs, I was
 not able to get a full console log. I add what I have.

 To the response (Cigaes), I should talk to the OS vendor if it crashes.
 As reported there is a reproducible access valuation of ffmpeg, writing in
 memory areas not allocated by ffmpeg or it’s processes. Why is the
 following crash a problem of the OS vendor?

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


More information about the FFmpeg-trac mailing list