Trial: build trunk with Oilpan everywhere.

third_party/WebKit/Source/core/frame/RemoteDOMWindow.h

Index: third_party/WebKit/Source/core/frame/RemoteDOMWindow.h
diff --git a/third_party/WebKit/Source/core/frame/RemoteDOMWindow.h b/third_party/WebKit/Source/core/frame/RemoteDOMWindow.h
index 35b796b6f92a2db4877f73615858a93587bc2459..1f5c4b136ae4a67df821fb86ca91fbc2dadce738 100644
--- a/third_party/WebKit/Source/core/frame/RemoteDOMWindow.h
+++ b/third_party/WebKit/Source/core/frame/RemoteDOMWindow.h
@@ -83,7 +83,7 @@ public:
 private:
     explicit RemoteDOMWindow(RemoteFrame&);
 
-    RawPtrWillBeMember<RemoteFrame> m_frame;
+    RawPtrWillBeWeakMember<RemoteFrame> m_frame;

[haraken, 2015/11/30 01:48:47]

I'm wondering why this needs to be a weak member.

[sof, 2015/11/30 06:25:47]

The RemoteDOMWindow will turn into the global object (and have a wrapper holding
it alive) in some unit tests (frame "swap" tests involving remote frames.)

So once the RemoteFrame becomes detached, the WebRemoteFrameImpl object just
drops the reference to it. But it is still kept alive via the wrapper holding
onto the RemoteDOMWindow and consequently not finalized (which will take down
the wrapper & the RemoteDOMWindow.) Break the undesirable dependency by making
this weak.

A one line fix to a leak that it took some time to understand; I hope we don't
have to mirror the explicit protocol between LocalFrame <-> LocalDOMWindow as
far as destruction steps are concerned. But I have my doubts.

 };
 
 } // namespace blink