Fix memory leak in PrerenderDispatcher.

chrome/renderer/prerender/prerender_dispatcher.cc

Index: chrome/renderer/prerender/prerender_dispatcher.cc
diff --git a/chrome/renderer/prerender/prerender_dispatcher.cc b/chrome/renderer/prerender/prerender_dispatcher.cc
index 84173fd444ce446cd96ffc3088347d2227732b53..c5af1cd2124095a1d99b2ee37fa710cc438416a6 100644
--- a/chrome/renderer/prerender/prerender_dispatcher.cc
+++ b/chrome/renderer/prerender/prerender_dispatcher.cc
@@ -12,11 +12,14 @@
 
 namespace prerender {
 
-PrerenderDispatcher::PrerenderDispatcher() {
-  WebKit::WebPrerenderingSupport::initialize(new PrerenderingSupport());
+PrerenderDispatcher::PrerenderDispatcher()
+    : prerendering_support_(new PrerenderingSupport()) {
+  WebKit::WebPrerenderingSupport::initialize(prerendering_support_.get());

[dominich, 2012/05/15 16:06:25]

this seems like an arbitrary place to put this. For 1, the Dispatcher isn't
dispatching anything. And 2, it has nothing to do with
WebKit::WebPrerenderingSupport. I wonder if this should be initialized/destroyed
directly in the chrome_content_render_client alongside the PrerenderDispatcher.

I wonder if we should somehow make the parallels between the Dispatcher and
Tracker more obvious. PrerenderBrowserTracker and PrerenderRenderTracker maybe?
or PrerenderRenderViewTracker and PrerenderUrlTracker?

[gavinp, 2012/05/18 05:46:25]

OK, the new patch does it this way.
Sounds good.  Do you want to create a bug for this, or do you think I should
pull that into this CL?

[jam, 2012/05/18 16:38:15]

it seems that CCRC has less to do with prerendering than this file..

 }
 
 PrerenderDispatcher::~PrerenderDispatcher() {
+  if (prerendering_support_.get())
+    WebKit::WebPrerenderingSupport::shutdown();
 }
 
 bool PrerenderDispatcher::IsPrerenderURL(const GURL& url) const {