Android: Explicitly tear-down the Native WebView.

The WebView will continue to evaluate JavaScript even after we've
released all handles to the WebView, to avoid this we'll call destroy()
when we release the WebView on our side. On Android 6.0 there's issued
a warning when destroy is called, but this is not fatal and seems to
be a know issue on their side. Alternatively, if it turns out that
calling destroy() causes problems in the future, it's possible to stop
JS evaluation by disabling it through the WebSettings interface.

Task-number: QTBUG-49664
Change-Id: Ic98d24d58525397ad06ecbc4476cd5613b6663ab
Reviewed-by: Eskil Abrahamsen Blomfeldt <eskil.abrahamsen-blomfeldt@theqtcompany.com>

src/jar/src/org/qtproject/qt5/android/view/QtAndroidWebViewController.java

@@ -445,4 +445,14 @@ public class QtAndroidWebViewController
         final PackageManager pm = view.getContext().getPackageManager();
         return pm.checkPermission("android.permission.ACCESS_FINE_LOCATION", name) == PackageManager.PERMISSION_GRANTED;
     }
+
+    public void destroy()
+    {
+        m_activity.runOnUiThread(new Runnable() {
+            @Override
+            public void run() {
+                m_webView.destroy();
+            }
+        });
+    }
 }

src/webview/qwebview_android.cpp

@@ -128,8 +128,13 @@ QAndroidWebViewPrivate::QAndroidWebViewPrivate(QObject *p)
 QAndroidWebViewPrivate::~QAndroidWebViewPrivate()
 {
     g_webViews->take(m_id);
-    if (m_window != 0 && m_window->parent() == 0)
+    if (m_window != 0) {
+        m_window->setVisible(false);
+        m_window->setParent(0);
         delete m_window;
+    }
+
+    m_viewController.callMethod<void>("destroy");
 }
 
 QUrl QAndroidWebViewPrivate::url() const