Bug 1431028 - Don't discard the back buffer in ClientSingleTiledLayerBuffer. r=mattwoodrow
authorJerryShih <hshih@mozilla.com>
Wed, 17 Jan 2018 02:19:00 -0500
changeset 454226 8a880591214558414d6a1c6a87280d65feb9dabf
parent 454225 f3dd2335e142f8effc6e80431a249943b5dbd221
child 454227 80b5219aedd81f12b2e234178a3ca1159fe49feb
push id1648
push usermtabara@mozilla.com
push dateThu, 01 Mar 2018 12:45:47 +0000
treeherdermozilla-release@cbb9688c2eeb [default view] [failures only]
perfherder[talos] [build metrics] [platform microbench] (compared to previous push)
reviewersmattwoodrow
bugs1431028
milestone59.0a1
first release with
nightly linux32
nightly linux64
nightly mac
nightly win32
nightly win64
last release without
nightly linux32
nightly linux64
nightly mac
nightly win32
nightly win64
Bug 1431028 - Don't discard the back buffer in ClientSingleTiledLayerBuffer. r=mattwoodrow MozReview-Commit-ID: HHbqlAnSVmN
gfx/layers/client/SingleTiledContentClient.cpp
--- a/gfx/layers/client/SingleTiledContentClient.cpp
+++ b/gfx/layers/client/SingleTiledContentClient.cpp
@@ -331,21 +331,15 @@ ClientSingleTiledLayerBuffer::PaintThebe
   // The new buffer is now validated, remove the dirty region from it.
   mTile.mInvalidBack.SubOut(tileDirtyRegion);
 
   dt = nullptr;
 
   mTile.Flip();
   UnlockTile(mTile);
 
-  if (backBuffer->HasIntermediateBuffer()) {
-    // If our new buffer has an internal buffer, we don't want to keep another
-    // TextureClient around unnecessarily, so discard the back-buffer.
-    mTile.DiscardBackBuffer();
-  }
-
   mValidRegion = aNewValidRegion;
   mLastPaintSurfaceMode = mode;
   mLastPaintContentType = content;
 }
 
 } // namespace layers
 } // namespace mozilla