It seems like latest trunk leaking mBuffer data in TextureClient/TextureHost Regression seems coming from: http://hg.mozilla.org/mozilla-central/rev/a283c87bafd1 MemoryTextureClient::Allocate - does alloc mBuffer MemoryTextureClient::~MemoryTextureClient - does not delete buffer because IsSharedWithCompositor == true TextureParent::ActorDestroy in case Deletion: does not call DeallocateSharedData because TEXTURE_DEALLOCATE_CLIENT =false and TEXTURE_DEALLOCATE_DEFERRED = true. so we jump onto mTextureHost->ForgetSharedData - which just forget mBuffer. - leak after all that we coming into MemoryTextureHost::DeallocateSharedData where mBuffer already null so no deletion happens

Comment on attachment 8364212 [details] [diff] [review] Don't drop mBuffer for deffered deallocate too early Review of attachment 8364212 [details] [diff] [review]: ----------------------------------------------------------------- Oh my, thanks!