Call AppIndexingReporter on AsyncTask

chrome/android/java/src/org/chromium/chrome/browser/AppIndexingUtil.java

Index: chrome/android/java/src/org/chromium/chrome/browser/AppIndexingUtil.java
diff --git a/chrome/android/java/src/org/chromium/chrome/browser/AppIndexingUtil.java b/chrome/android/java/src/org/chromium/chrome/browser/AppIndexingUtil.java
index 4e4aca058b446417c865412c358189ba45edb456..2f939ff24fed3f88b9643789dc6dc81ecd0cf5a4 100644
--- a/chrome/android/java/src/org/chromium/chrome/browser/AppIndexingUtil.java
+++ b/chrome/android/java/src/org/chromium/chrome/browser/AppIndexingUtil.java
@@ -4,6 +4,7 @@
 
 package org.chromium.chrome.browser;
 
+import android.os.AsyncTask;
 import android.webkit.URLUtil;
 
 import org.chromium.base.SysUtils;
@@ -40,9 +41,14 @@ public class AppIndexingUtil {
         CopylessPaste copylesspaste = interfaces.getInterface(CopylessPaste.MANAGER);
         copylesspaste.getEntities(new CopylessPaste.GetEntitiesResponse() {
             @Override
-            public void call(WebPage webpage) {
+            public void call(final WebPage webpage) {
                 if (webpage == null) return;
-                AppIndexingReporter.getInstance().reportWebPage(webpage);
+                AsyncTask.execute(new Runnable() {

[wychen, 2017/04/10 23:22:23]

Probably makes sense to move AsyncTask to downstream, since upstream caller
doesn't "know" the details of the downstream implementation details.

[dproctor, 2017/04/10 23:23:16]

Sure, that makes sense.

+                    @Override
+                    public void run() {
+                        AppIndexingReporter.getInstance().reportWebPage(webpage);
+                    }
+                });
             }
         });
     }