vp9 encoder crash on snow, qjoe, worldwarz, red, 3dtv, birds, and garden videos

[GoogleCodeExporter]

What is the expected behavior?
encodes

What do you see instead?
crash
returncode -1073741819

What version are you using?
sept 14 build VP9 Encoder v1.2.0-4277-gc73e441

On what operating system?
Win64

Can you reproduce using the vpxdec or vpxenc tools?
Yes

What command line are you using?
First pass, which is okay
vpxenc --cpu-used=1 -t 1 -w 1920 -h 1080 --fps=30000/1001 --target-bitrate=2000 
snow.1920x1080_30Hz_P420.yuv -o snow0.tmp.vp9.webm --fpf=snow_vp9.fpf -p 2 
--pass=1 --codec=vp9 --good --lag-in-frames=25 --min-q=0 --max-q=63 
--end-usage=vbr --auto-alt-ref=1 --kf-max-dist=9999 --kf-min-dist=0 
--drop-frame=0 --static-thresh=0 --bias-pct=50 --minsection-pct=0 
--maxsection-pct=2000 --arnr-maxframes=7 --arnr-strength=5 --arnr-type=3 
--sharpness=0 --undershoot-pct=100 -v --psnr 

Second pass, which crashes
vpxenc --cpu-used=1 -t 1 -w 1920 -h 1080 --fps=30000/1001 --target-bitrate=2000 
snow.1920x1080_30Hz_P420.yuv -o snow0.tmp.vp9.webm --fpf=snow_vp9.fpf -p 2 
--pass=2 --codec=vp9 --good --lag-in-frames=25 --min-q=0 --max-q=63 
--end-usage=vbr --auto-alt-ref=1 --kf-max-dist=9999 --kf-min-dist=0 
--drop-frame=0 --static-thresh=0 --bias-pct=50 --minsection-pct=0 
--maxsection-pct=2000 --arnr-maxframes=7 --arnr-strength=5 --arnr-type=3 
--sharpness=0 --undershoot-pct=100 -v --psnr 

Please provide any additional information below.
Worked with sept 11 build VP9 Encoder v1.2.0-4247-g65fe7d7
Affects multiple videos, snow, qjoe, 3dtv, worldwarz, red, birds, and garden
reproduces quickest with snow, or qjoe.

Original issue reported on code.google.com by fbarch...@google.com on 14 Sep 2013 at 8:56

[GoogleCodeExporter]

sep 15 (sunday) and sep 16 (monday) are the same version and also reproduce the 
issue.
sep 11 (last wednesday) works.  VP9 Encoder v1.2.0-4247-g65fe7d7
all cpu-used levels work on snow.

cpu-used=1: crash
Pass 2/2 frame  120/95    123957B   40584 ms 2.96 fps [ETA  0:40:11] 
←[K36.796 35.227 45.713 45.628    1263FFFF93F

cpu-used=2: crash
Pass 2/2 frame   55/30      8124B 4119944 us 13.35 fps [ETA  0:15:30] 
←[K45.020 43.838 50.797 48.172     259FFF07F  

cpu-used=3, 4, 5: ok

On qjoe
vpxenc --cpu-used=2 -t 1 -w 1920 -h 800 --fps=15000/1001 --target-bitrate=2000 
qjoe.1920x800_15Hz_P420.yuv -o qjoe0.tmp.vp9.webm --fpf=qjoe_vp9.fpf -p 2 
--pass=2 --codec=vp9 --good --lag-in-frames=25 --min-q=0 --max-q=63 
--end-usage=vbr --auto-alt-ref=1 --kf-max-dist=9999 --kf-min-dist=0 
--drop-frame=0 --static-thresh=0 --bias-pct=50 --minsection-pct=0 
--maxsection-pct=2000 --arnr-maxframes=7 --arnr-strength=5 --arnr-type=3 
--sharpness=0 --undershoot-pct=100 -v --psnr 

crashes here: Pass 2/2 frame  275/250  3411192B  146281 ms 1.88 fps

Original comment by fbarch...@google.com on 16 Sep 2013 at 6:56

[GoogleCodeExporter]

Initial investigation appears to indicate the problem arise from use of invalid 
motion vector in motion search. Here is a proposed fix: 

https://gerrit.chromium.org/gerrit/#/c/67191

Original comment by ya...@google.com on 16 Sep 2013 at 7:53

• Changed state: Started

[GoogleCodeExporter]

Fix confirmed in VP9 Encoder v1.2.0-4282-gf582aa6

Original comment by fbarch...@google.com on 17 Sep 2013 at 7:02

[GoogleCodeExporter]

Original comment by ya...@google.com on 17 Sep 2013 at 4:19

• Changed state: Fixed