Move Renderer-side NPObject owner tracking to JavaBridgeChannel.

content/browser/renderer_host/java/java_bound_object.h

Index: content/browser/renderer_host/java/java_bound_object.h
diff --git a/content/browser/renderer_host/java/java_bound_object.h b/content/browser/renderer_host/java/java_bound_object.h
index ff97fdb2b6c379178ad9f5a2267e91e084f97d29..8891317b6de933ded1369431ab1769892a00195f 100644
--- a/content/browser/renderer_host/java/java_bound_object.h
+++ b/content/browser/renderer_host/java/java_bound_object.h
@@ -34,9 +34,10 @@ class JavaBoundObject {
   // JavascriptInterface annotation are exposed to JavaScript.  This property
   // propagates to all Objects that get implicitly exposed as return values as
   // well. Returns an NPObject with a ref count of one which owns the
-  // JavaBoundObject.
+  // JavaBoundObject. The object is marked as owned by |owner|.
   // See also comment below for |manager_|.
   static NPObject* Create(
+      struct _NPP* owner,

[joth, 2013/07/02 20:49:03]

I thought in C++ it's fine to just declare this as "_NPP* owner" no 'struct'
needed, and chrome convention is to do it that way? (I have no strong opinion on
it though)

[Wez, 2013/07/02 21:05:09]

Yes. However, the NPAPI headers typedef struct _NPP to NPP, so we've used struct
_NPP for consistency.

       const base::android::JavaRef<jobject>& object,
       const base::android::JavaRef<jclass>& safe_annotation_clazz,
       const base::WeakPtr<JavaBridgeDispatcherHostManager>& manager);