Added a call to hide the popup when the render process dies.

content/public/android/java/src/org/chromium/content/browser/ContentViewCore.java

Index: content/public/android/java/src/org/chromium/content/browser/ContentViewCore.java
diff --git a/content/public/android/java/src/org/chromium/content/browser/ContentViewCore.java b/content/public/android/java/src/org/chromium/content/browser/ContentViewCore.java
index eac7cf399f153f1eee3fd49092f8c66cec186d3d..d03293b5ef9279e5df45e3f8aa5f1682e7c3aba4 100644
--- a/content/public/android/java/src/org/chromium/content/browser/ContentViewCore.java
+++ b/content/public/android/java/src/org/chromium/content/browser/ContentViewCore.java
@@ -734,6 +734,11 @@ public class ContentViewCore
                 resetScrollInProgress();
                 resetGestureDetectors();
             }
+
+            @Override
+            public void renderProcessGone(boolean wasOomProtected) {
+                hidePopupDialog();

[jdduke (slow), 2014/04/10 14:02:04]

If the ContentViewCore persists (permanently) after the renderer is destroyed,
we'll want to also call |resetScrollInProgress()| and |resetGestureDetectors()|.
 I'm not exactly sure what the relative lifetimes are...

[jdduke (slow), 2014/04/11 00:11:00]

Yeah, turns out we'll want to call both of the mentioned methods, good catch.

+            }
         };
     }