cc: Test losing the output surface during deferred commits.

cc: Test losing the output surface during deferred commits.

This adds a unit test that would fail after landing
the https://codereview.chromium.org/287193003 CL without any further
changes, documenting one regression it caused.

R=brianderson, enne
BUG=376649, 374287
Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=276428

[enne (OOO), 2014-06-10 18:43:33]

https://codereview.chromium.org/321193002/diff/1/cc/trees/layer_tree_host_uni...
File cc/trees/layer_tree_host_unittest_context.cc (right):

https://codereview.chromium.org/321193002/diff/1/cc/trees/layer_tree_host_uni...
cc/trees/layer_tree_host_unittest_context.cc:1508:
MainThreadTaskRunner()->PostTask(
This seems racy.  Couldn't DeferCommitsOnMainThread(true),
LoseContextOnImplThread, and DeferCommitsOnMainThread(false) all occur before
the BeginFrame arrives?

[danakj, 2014-06-10 18:46:24]

https://codereview.chromium.org/321193002/diff/1/cc/trees/layer_tree_host_uni...
File cc/trees/layer_tree_host_unittest_context.cc (right):

https://codereview.chromium.org/321193002/diff/1/cc/trees/layer_tree_host_uni...
cc/trees/layer_tree_host_unittest_context.cc:1508:
MainThreadTaskRunner()->PostTask(
On 2014/06/10 18:43:32, enne wrote:
> This seems racy.  Couldn't DeferCommitsOnMainThread(true),
> LoseContextOnImplThread, and DeferCommitsOnMainThread(false) all occur before
> the BeginFrame arrives?

I think not because after ScheduledActionWillSendBeginMainFrame() returns, we
will post the BeginMainFrame to the main thread, so that task is always posted
before this method here runs and posts.

[enne (OOO), 2014-06-10 18:59:43]

lgtm

https://codereview.chromium.org/321193002/diff/1/cc/trees/layer_tree_host_uni...
File cc/trees/layer_tree_host_unittest_context.cc (right):

https://codereview.chromium.org/321193002/diff/1/cc/trees/layer_tree_host_uni...
cc/trees/layer_tree_host_unittest_context.cc:1508:
MainThreadTaskRunner()->PostTask(
Oh, right.  ScheduledActionWillSendBeginMainFrame is happening on the compositor
thread.

[enne (OOO), 2014-06-10 18:59:49]

The CQ bit was checked by enne@chromium.org

[commit-bot: I haz the power, 2014-06-10 19:02:31]

CQ is trying da patch. Follow status at
 https://chromium-status.appspot.com/cq/danakj@chromium.org/321193002/1

[commit-bot: I haz the power, 2014-06-10 23:53:09]

FYI, CQ is re-trying this CL (attempt #1).
The failing builders are:
  win_chromium_x64_rel on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/win_chromium_x64_rel/...)

[commit-bot: I haz the power, 2014-06-11 11:54:33]

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

[commit-bot: I haz the power, 2014-06-11 11:54:34]

Try jobs failed on following builders:
  win_chromium_x64_rel on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/win_chromium_x64_rel/...)

[danakj, 2014-06-11 14:14:30]

The CQ bit was checked by danakj@chromium.org

[commit-bot: I haz the power, 2014-06-11 14:15:32]

CQ is trying da patch. Follow status at
 https://chromium-status.appspot.com/cq/danakj@chromium.org/321193002/1

[commit-bot: I haz the power, 2014-06-11 16:30:40]

Change committed as 276428