commit | 8dd3d3a2d488b258e395e783b0520ac413f4d938 | [log] [tgz] |
---|---|---|
author | Fergal Daly <[email protected]> | Tue May 12 16:40:33 2020 |
committer | Commit Bot <[email protected]> | Tue May 12 16:40:33 2020 |
tree | 4777bceb99a9a5dcfd0a2985cf3c42f89b4c5f18 | |
parent | 48d38b8ac5140257d4c7019eb0938ee91d9b6c72 [diff] |
Fix another way to crash as in https://crbug.com/1006814. This is very similar to https://crrev.com/c/2159389 WebContentsAndroid::EvaluateJavaScript calls WebContentsImpl::CreateRenderViewForInitialEmptyDocument even when it is not the initial empty document. If the main frame has crashed, this causes it to be reused even with RenderDocument set to not reuse crashed frames. This fix is the same as before. Rename InitializeRenderFrameForDebugURLIfNecessary to InitializeRenderFrameForImmediateUse. It's now OK to call this unconditionally and now it is called from the newly-added WebContentsAndroid::InitializeRenderFrameForJavaScript which is used from all of the WebView APIs for evaluating JS in a frame. This adds a Java test from webview. In the process it moves a bunch of local variables to be members of the test class. I can factor that out into a different CL, if desired, it should be a no-op. Bug: 1006814 Change-Id: Ib111065840c57511fba0bdcfbccb5301d6c3e997 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2186901 Commit-Queue: Fergal Daly <[email protected]> Reviewed-by: Bo <[email protected]> Reviewed-by: Alex Moshchuk <[email protected]> Auto-Submit: Fergal Daly <[email protected]> Cr-Commit-Position: refs/heads/master@{#767833}
Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.
The project's web site is https://www.chromium.org.
Documentation in the source is rooted in docs/README.md.
Learn how to Get Around the Chromium Source Code Directory Structure .
For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.