Bug 1341496 - Part 2: Don't use a separate ReadLock for the second component alpha texture as they should always be locked/unlocked at the same time. r=nical, a=gchang
authorMatt Woodrow <mwoodrow@mozilla.com>
Wed, 19 Apr 2017 15:16:13 +1200
changeset 396049 b38f7851fe6fca0dd759ed186b4986ed495b66e3
parent 396048 8f4eea328bd54402f72e32e4f9a6f7991867eaf2
child 396050 3eb1077706330f164be580efe5b039f3114e0cda
push id1468
push userasasaki@mozilla.com
push dateMon, 05 Jun 2017 19:31:07 +0000
treeherdermozilla-release@0641fc6ee9d1 [default view] [failures only]
perfherder[talos] [build metrics] [platform microbench] (compared to previous push)
reviewersnical, gchang
bugs1341496
milestone54.0
Bug 1341496 - Part 2: Don't use a separate ReadLock for the second component alpha texture as they should always be locked/unlocked at the same time. r=nical, a=gchang
gfx/layers/client/ContentClient.cpp
--- a/gfx/layers/client/ContentClient.cpp
+++ b/gfx/layers/client/ContentClient.cpp
@@ -327,17 +327,19 @@ ContentClientRemoteBuffer::CreateBackBuf
       mForwarder->GetCompositorBackendType(),
       mTextureFlags | ExtraTextureFlags(),
       TextureAllocationFlags::ALLOC_CLEAR_BUFFER_WHITE
     );
     if (!mTextureClientOnWhite || !AddTextureClient(mTextureClientOnWhite)) {
       AbortTextureClientCreation();
       return;
     }
-    mTextureClientOnWhite->EnableBlockingReadLock();
+    // We don't enable the readlock for the white buffer since we always
+    // use them together and waiting on the lock for the black
+    // should be sufficient.
   }
 }
 
 void
 ContentClientRemoteBuffer::CreateBuffer(ContentType aType,
                                         const IntRect& aRect,
                                         uint32_t aFlags,
                                         RefPtr<gfx::DrawTarget>* aBlackDT,