Handle failed GpuMemoryBuffer allocations properly.

Handle failed GpuMemoryBuffer allocations properly.

It is possible for an allocation to fail on the gpu side, we should handle it gracefully.
Currently we DCHECK that it succeeded in the browser, which in release leads to unexpected behaviour and NOTREACHED hit during destruction on the gpu side.

BUG=

Committed: https://crrev.com/34667610c029b3ca2faaf188e8f34cc1a726a1b6
Cr-Commit-Position: refs/heads/master@{#302721}

[alexst (slow to review), 2014-11-04 20:58:19]

Patchset #1 (id:1) has been deleted

[alexst (slow to review), 2014-11-04 21:38:09]

alexst@chromium.org changed reviewers:
+ piman@chromium.org, reveman@chromium.org

[piman, 2014-11-04 21:43:38]

lgtm

[reveman, 2014-11-04 22:31:30]

lgtm

[alexst (slow to review), 2014-11-04 23:29:07]

The CQ bit was checked by alexst@chromium.org

[commit-bot: I haz the power, 2014-11-04 23:29:57]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/701873005/20001

[commit-bot: I haz the power, 2014-11-05 00:35:30]

Committed patchset #1 (id:20001)

[commit-bot: I haz the power, 2014-11-05 00:36:02]

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