Fix a fuzzer crash in VideoFramePool

Fix a fuzzer crash in VideoFramePool

It seems that providing random data to the VPX parser can make it call the video
frame pool with illegal parameters. This currently causes a crash, let's make it
return null, and the calling code already seems to handle that well.

BUG=648849
Committed: https://crrev.com/2ba53c9cf88833aabbb642e53de195fb150e28f0
Cr-Commit-Position: refs/heads/master@{#420443}

[hubbe, 2016-09-22 18:55:18]

hubbe@chromium.org changed reviewers:
+ dalecurtis@google.com

[hubbe, 2016-09-22 18:55:27]

The CQ bit was checked by hubbe@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2016-09-22 18:55:56]

Dry run: CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[DaleCurtis, 2016-09-22 19:11:53]

dalecurtis@chromium.org changed reviewers:
+ dalecurtis@chromium.org

[DaleCurtis, 2016-09-22 19:11:54]

lgtm

[commit-bot: I haz the power, 2016-09-22 20:14:53]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-09-22 20:14:54]

Dry run: This issue passed the CQ dry run.

[hubbe, 2016-09-22 20:17:14]

The CQ bit was checked by hubbe@chromium.org

[commit-bot: I haz the power, 2016-09-22 20:18:13]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-09-22 20:24:24]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-09-22 20:30:18]

Description was changed from

==========
Fix a fuzzer crash in VideoFramePool

It seems that providing random data to the VPX parser can make it call the video
frame pool with illegal parameters. This currently causes a crash, let's make it
return null, and the calling code already seems to handle that well.

BUG=648849
==========

to

==========
Fix a fuzzer crash in VideoFramePool

It seems that providing random data to the VPX parser can make it call the video
frame pool with illegal parameters. This currently causes a crash, let's make it
return null, and the calling code already seems to handle that well.

BUG=648849

Committed: https://crrev.com/2ba53c9cf88833aabbb642e53de195fb150e28f0
Cr-Commit-Position: refs/heads/master@{#420443}
==========

[commit-bot: I haz the power, 2016-09-22 20:30:20]

Patchset 1 (id:??) landed as
https://crrev.com/2ba53c9cf88833aabbb642e53de195fb150e28f0
Cr-Commit-Position: refs/heads/master@{#420443}