Log in

View Full Version : x264 Runtime error crash


jsevakis
29th April 2010, 22:11
I can't figure this out, so I'm hoping someone here can help me.

I do encodes in massive batches using CLI. Lately I've been getting runtime library errors during encodes. They're seemingly random, and they happen at any time during either pass 1 or pass 2.

Right now, they're Microsoft Visual C++ Runtime Library errors under the current x264.nl build ("This application has requested the Runtime to terminate it in an unusual way"), but an earlier GCC build had similar GCC runtime errors. I've tried several official and unofficial builds with similar errors.

I'm hardly new to x264 CLI (or big batches of encodes) and this is a pretty recent development. I thought initially that it was because I upgraded to dgmpgdec 1.5.8, but after downgrading back to 1.4.9 I'm still having these errors. Nothing has changed with the PC or AviSynth either.

Here are my command lines. I'm using XP Pro SP3 x86. Any help in figuring out how to fix this would be really appreciated.

x264.exe --profile main --tune animation -p 1 --stats "%~n1.avs.log" -B 552 -o nul "%~n1.avs"
x264.exe --profile main --tune animation -p 2 --stats "%~n1.avs.log" -B 552 -o "%~n1.mp4" "%~n1.avs"

Later in the script I make an LQ version, which seems to be less problematic:
x264.exe --profile baseline --tune animation --stats "%~n1.avs.log" -B 352 -o "%~n1.mp4" "%~n1.avs"

Dark Shikari
29th April 2010, 22:50
Sounds like a decoder or filter crash. Check where the crash log says the crash occurred.

jsevakis
29th April 2010, 23:49
Since it's not a real "crash" to Windows (there's no "I'm gonna tell Microsoft about this, 'kay?" dialogue), I don't know where to find a log like that. Does x264 generate one when it's not a debug build? (I did search the forum, but couldn't find anything specifically referencing an x264 crash log.)

video_magic
30th April 2010, 00:10
Do a few virus scans (not at the same time) with a couple of up-to-date reputable antivirus scanners. The reason I suggest doing more than one scan is that no single antivirus program could find them all.

I had a similar message last year - turns out a virus had infected many of my exe files.

jsevakis
30th April 2010, 03:19
Passed both Avast and AVG with no issues. Guess we can rule that out. Thanks for the tip tho.