LayoutTests: migrate nested-plugin-objects to ppapi

ppapi/proxy/plugin_var_tracker.cc

 // Copyright (c) 2012 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
 #include "ppapi/proxy/plugin_var_tracker.h"
 
 #include <stddef.h>
 
 #include "base/memory/ref_counted.h"
 #include "base/memory/singleton.h"
@@ skipping 389 matching lines @@
   DCHECK(iter->second.ref_count == 0);
   SendReleaseObjectMsg(*object);
 
   UserDataToPluginImplementedVarMap::iterator found =
       user_data_to_plugin_.find(object->user_data());
   if (found != user_data_to_plugin_.end()) {
     // This object is implemented in the plugin.
     if (found->second.instance == 0) {
       // Instance is destroyed. This means that we'll never get a Deallocate
       // call from the renderer and we should do so now.
-      found->second.ppp_class->Deallocate(found->first);
+      CallWhileUnlocked(found->second.ppp_class->Deallocate, found->first);
       user_data_to_plugin_.erase(found);
     } else {
       // The plugin is releasing its last reference to an object it implements.
       // Clear the tracking data that links our "plugin implemented object" to
       // the var. If the instance is destroyed and there is no ID, we know that
       // we should just call Deallocate on the object data.
       //
       // See the plugin_object_id declaration for more info.
       found->second.plugin_object_id = 0;
     }
@@ skipping 86 matching lines @@
     int id,
     PP_Instance instance,
     base::SharedMemoryHandle* handle,
     uint32_t* size_in_bytes) {
   NOTREACHED();
   return false;
 }
 
 }  // namesace proxy
 }  // namespace ppapi