Log in

View Full Version : x264 crash - 100% repeatability (at least for me)

pokazene_maslo
13th November 2012, 19:30
Hi.

I'm trying to encode ProRes file but x264 is crashing just at start.

source file: 1280x720, 4:2:2, 10 bit, mov container
x264: r2230, 64bit 10bit-depth from x264.nl
LAV filters 0.53.2
encoding parameters: x264x64b10.exe --crf 10 --preset veryslow --profile high422 --level 3.1 --ref 5 --merange 32 --output-csp i422 --demuxer lavf --psnr --ssim -o 01.mkv 01.mov

system: win7x64, C2D e6300

Problem signature:
Problem Event Name: APPCRASH
Application Name: x264x64b10.exe
Application Version: 0.129.2230.0
Application Timestamp: 509d1b6e
Fault Module Name: StackHash_5bd2
Fault Module Version: 6.1.7601.17725
Fault Module Timestamp: 4ec4aa8e
Exception Code: c0000374
Exception Offset: 00000000000c40f2
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1051
Additional Information 1: 5bd2
Additional Information 2: 5bd2cc000ccd753f91f7121500673973
Additional Information 3: a420
Additional Information 4: a420b99dc5720f68ec2923ff7e31a821

Just for the record. File playback in MPC-HC through LAV filters is working.
MasterNobody
13th November 2012, 19:55
Most probably that is bug in lavf library (ffmpeg/libav) and it would probably work with --demuxer ffms or --demuxer avs (in case of 32-bit if you have AviSynth). So it would be better to bug report ffmpeg/libav developers (of course after testing with the latest ffmpeg/avconv).
pokazene_maslo
13th November 2012, 20:00
with FFMS it's working but that doesn't excludes bug in x264
LoRd_MuldeR
13th November 2012, 20:21
As MasterNobody said,

if this happens only with a specific type on input file ("ProRes") and only with the "lavf" demuxer, then it very clearly indicates a bug in the lavf library (that your x264 binary was built with) rather than a bug in x264 itself.

Either that or a borked build. Did you build x264 yourself? If so, did you try different versions of libavf? Otherwise, whose build are you using and did you try different builds?
pokazene_maslo
13th November 2012, 20:39
I use this x264 http://mirror01.x264.nl/x264/64bit/10bit_depth/revision2230/x264.exe
MasterNobody
13th November 2012, 21:00
Looks like it is bug with the way x264 use lavf and the latest changes in lavf itself. Will be fixed in next release.
sneaker_ger
13th November 2012, 21:45
Fixed:
https://github.com/DarkShikari/x264-devel/commit/f4aee0e77c9932e8b085d93eef5e97bbc04c8738