Move cache clearing from AwRenderViewExt to AwRenderFrameExt.

android_webview/renderer/aw_render_view_ext.cc

Index: android_webview/renderer/aw_render_view_ext.cc
diff --git a/android_webview/renderer/aw_render_view_ext.cc b/android_webview/renderer/aw_render_view_ext.cc
index eaec17844e3dbb6c04f649d71a41de5da38e115c..c14f14e1c9a7c68f006597484655657a8b335825 100644
--- a/android_webview/renderer/aw_render_view_ext.cc
+++ b/android_webview/renderer/aw_render_view_ext.cc
@@ -7,7 +7,6 @@
 #include "content/public/renderer/render_frame.h"
 #include "content/public/renderer/render_view.h"
 #include "third_party/WebKit/public/web/WebFrame.h"
-#include "third_party/WebKit/public/web/WebImageCache.h"
 #include "third_party/WebKit/public/web/WebView.h"
 
 namespace android_webview {
@@ -66,15 +65,4 @@ void AwRenderViewExt::CheckContentsSize() {
         contents_size));
 }
 
-void AwRenderViewExt::Navigate(const GURL& url) {
-  // Navigate is called only on NEW navigations, so WebImageCache won't be
-  // freed when the user just clicks on links, but only when a navigation is
-  // started, for instance via loadUrl. A better approach would be clearing the
-  // cache on cross-site boundaries, however this would require too many
-  // changes both on the browser side (in RenderViewHostManger), to the
-  // IPCmessages and to the RenderViewObserver. Thus, clearing decoding image
-  // cache on Navigate, seems a more acceptable compromise.
-  blink::WebImageCache::clear();
-}
-
 }  // namespace android_webview