aw: Check isDestroyedOrNoOperation for shouldOverrideUrlLoading
Two reasons. One is that these callbacks should not happen if renderer process crashed. Looks like this (and a few others) are missed because they are synchronous and called from AwContentsClient instead of AwContentsClientCallbackHelper. Second reason which is relevant to the bug is that we should not callback to the app if webview is already destroyed. This can happen when a native->java jni call uses a jweak which can resurrect objects that are effectively destroyed already. Bug: 824156 Change-Id: I0a8d59e2f36070d7a4c53242ce077bda3c9bfe73 Reviewed-on: https://chromium-review.googlesource.com/981433Reviewed-by:Bo <boliu@chromium.org> Reviewed-by:
Richard Coles <torne@chromium.org> Commit-Queue: Bo <boliu@chromium.org> Cr-Commit-Position: refs/heads/master@{#546158}
Showing
Please register or sign in to comment