APPCRASH - crashing with adaptive quantizer
Issue #100
resolved
When calling:
mencoder -lavdopts threads=8 -really-quiet -of rawvideo -o - -ovc raw
-vf scale,format=i420 -sws 10 -forcedsubsonly -nosub -nosound -mc 0 "H:\Temp\enc
odingTempAvisynthSkript_07_39_23_1110.avs" | ffmpeg -loglevel fatal -threads 8 -
threads 8 -an -sn -r 25 -pix_fmt yuv420p -s 704x480 -f rawvideo -i - -r 25 -pix_
fmt yuv420p10le -f rawvideo - | x265-16bit --pmode --pme --input - --input-depth
10 --input-res 704x480 --fps 25 --profile main10 --no-high-tier --no-open-gop -
-qpfile "H:\Temp\test_07_39_23_1110_06.qp" --aq-strength 1.5 --cu-l
ossless --colormatrix bt470bg --output "H:\Temp\test_07_39_23_1110_
07.265"
x265 crashes
yuv [info]: 704x480 fps 25000/1000 i420p10 unknown frame count
x265 [info]: HEVC encoder version 1.4+380-9d26082ca7b3
x265 [info]: build info [Windows][GCC 4.8.2][64 bit] 16bpp
x265 [info]: using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.2 AVX AVX2 FMA3 LZ
CNT BMI2
x265 [info]: Main 10 profile, Level-3 (Main tier)
x265 [info]: WPP streams / frame threads / pool : 8 / 3 / 8 / pme / pmode
x265 [info]: Internal bit depth : 10
x265 [info]: CTU size / RQT depth inter / intra : 64 / 1 / 1
x265 [info]: ME / range / subpel / merge : hex / 57 / 2 / 2
x265 [info]: Keyframe min / max / scenecut : 25 / 250 / 40
x265 [info]: Lookahead / bframes / badapt : 20 / 4 / 2
x265 [info]: b-pyramid / weightp / weightb / refs: 1 / 1 / 0 / 3
x265 [info]: Rate Control / AQ-Strength / CUTree : CRF-28.0 / 1.5 / 1
x265 [info]: tools: rd=3 deblock sao signhide tmvp cu-lossless
84 frames: 21.95 fps, 118.91 kb/s
Problem signature:
Problem Event Name: APPCRASH
Application Name: x265-16bit.exe
Application Version: 1.4.0.380
Application Timestamp: 54b663f7
Fault Module Name: x265-16bit.exe
Fault Module Version: 1.4.0.380
Fault Module Timestamp: 54b663f7
Exception Code: c0000005
Exception Offset: 0000000000150d90
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1031
Additional Information 1: e554
Additional Information 2: e5549f10e50fcf78768030a8825c35da
Additional Information 3: b413
Additional Information 4: b413b7f30b48f8fa4ef3918c7e4e2b6f
Comments (4)
-
reporter -
there was a general bug in --cu-lossless for a short while. --aq-strength was probably just making it easier to reproduce.
Is this crash still reproducible?
-
reporter no it's fixed in the current version
-
- changed status to resolved
resolved
- Log in to comment
removing '--aq-strength 1.5 ' or '--cu-lossless' from the command line seems to 'fix' the issue -> seems like there is a problem with '--aq-strength' in combination with '--cu-lossless'