[vp9 dec] Illegal memory access when stream starts with invisible intra frame.

[GoogleCodeExporter]

What is the expected behavior? What do you see instead?
For some test streams decoder reports that some frames are corrupted. Number is 
different from launch to launch and may be larger then number of frames in the 
bitstream.

Problem occurs when the first frame in the stream is hidden and 
ctx->last_show_frame isn't set to valid value.

What version are you using? On what operating system?
Recent snapshot.
Revision: 2ed0cf06f9984a6c1ae2762c9fa0b5347027fbc6
Date: 08-Apr-15 06:57:21

Win 8.1, x64 VS2013 build.

Please provide any additional information below.

Proposed fix
https://gerrit.chromium.org/gerrit/#/c/74305/

Original issue reported on code.google.com by ru.xa...@gmail.com on 8 Apr 2015 at 4:32

[GoogleCodeExporter]

Original comment by ya...@google.com on 7 May 2015 at 10:31

• Changed state: Assigned

[GoogleCodeExporter]

Hi Alexander,
Thanks for picking up on this. Do you have a test stream that demonstrates the 
problem that you can share with us?
Thanks.

Original comment by agra...@google.com on 7 May 2015 at 10:48

• Changed state: Started

[GoogleCodeExporter]

Hi Adrian,
Do you have access to Intel Stress Bitstreams?
In our set, files with 210th index are definite reproducers. Filename mask for 
them is Syntax_VP9_*_210_*.vp9

Original comment by ru.xa...@gmail.com on 12 May 2015 at 11:35