Pepper WebSocket API: Fix memory leak issue

ppapi/native_client/src/shared/ppapi_proxy/browser_callback.cc

Index: ppapi/native_client/src/shared/ppapi_proxy/browser_callback.cc
diff --git a/ppapi/native_client/src/shared/ppapi_proxy/browser_callback.cc b/ppapi/native_client/src/shared/ppapi_proxy/browser_callback.cc
index 5f5e7c36e8df810bfb20b1b652f90d43c4fedf3e..debb0bf5ab3215ecc942504d22ceb6fb5b68bf4b 100644
--- a/ppapi/native_client/src/shared/ppapi_proxy/browser_callback.cc
+++ b/ppapi/native_client/src/shared/ppapi_proxy/browser_callback.cc
@@ -89,6 +89,7 @@ void RunRemoteCallback(void* user_data, int32_t result) {
     read_buffer_size = kMaxReturnVarSize;
     read_buffer.reset(
         Serialize(&remote_callback->read_var, 1, &read_buffer_size));
+    PPBVarInterface()->Release(remote_callback->read_var);

[Takashi Toyoshima, 2012/09/07 17:18:27]

This is a renderer process side memory leak.

[dmichael (off chromium), 2012/09/07 18:36:58]

Nice catch!

I have automatic checking for the plugin side for all tests (see test_case.h and
test_case.cc). I'm surprised this isn't showing up in the tests? Maybe we just
aren't reusing a var there?

In any case, I definitely should extend it to check the renderer side...

   }
 
   NaClSrpcError srpc_result =