Revert of cc: Stop blocking the main thread in...
Revert of cc: Stop blocking the main thread in CreateAndInitializeOutputSurface. (https://codereview.chromium.org/287193003/) Reason for revert: This may be causing mac browser test flakiness: https://code.google.com/p/chromium/issues/detail?id=376649 Original issue's description: > cc: Stop blocking the main thread in CreateAndInitializeOutputSurface. > > The ThreadProxy does not need to block the main thread anymore, instead > have it post back DidInitializeOutputSurface() with the result of the > process. > > We would delete all contents textures on the compositor thread during > OutputSurface creation, which doesn't really make sense, cuz the > ResourceProvider won't be the same one anymore, and this required > blocking the thread. > > We also notified the main thread that the OutputSurface was lost when > creating the new output surface. > > Instead, post a DidLoseOutputSurface() to the main thread to inform > the LayerTreeHost right away, and have that block and clean up > the contents textures immediately (to be removed when we always do > impl-side painting). > > R=enne > BUG=374287 > > Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=272276 TBR=enne@chromium.org NOTREECHECKS=true NOTRY=true BUG=374287 Review URL: https://codereview.chromium.org/299233002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@272580 0039d316-1c4b-4281-b951-d872f2087c98
Showing
Please register or sign in to comment