Fix resource leaks in CDM implementation.

webkit/media/crypto/ppapi/cdm_wrapper.cc

Index: webkit/media/crypto/ppapi/cdm_wrapper.cc
diff --git a/webkit/media/crypto/ppapi/cdm_wrapper.cc b/webkit/media/crypto/ppapi/cdm_wrapper.cc
index 88baa44062b74920ed0ee272db53ec8c29824e7b..0a4392c79294136312644aa2d865f4560301f1c9 100644
--- a/webkit/media/crypto/ppapi/cdm_wrapper.cc
+++ b/webkit/media/crypto/ppapi/cdm_wrapper.cc
@@ -234,6 +234,7 @@ bool CdmWrapper::Decrypt(pp::Buffer_Dev encrypted_buffer,
       output_buffer,
       encrypted_block_info.tracking_info));
 
+  pp::Module::Get()->core()->ReleaseResource(encrypted_buffer.pp_resource());

[xhwang, 2012/09/05 09:26:55]

Is this ReleaseResource called because we are passing in pp::Buffer_Dev by
value? Can we pass by const reference to avoid this?

If we really need to call it here, move it right after cdm_->Decrypt() call?

[Tom Finegan, 2012/09/05 16:04:41]

ReleaseResource must be called in some manner. The browser owns the last
reference on the PP_Resource. Using scoper to hide the gory details in latest
patch.

   return true;
 }