New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 613781 link

Starred by 4 users

Issue metadata

Status: Fixed
Owner:
inactive
Closed: Jun 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 1
Type: Bug-Regression



Sign in to add a comment

WebView multiprocess: blank screen after cross domain navigation.

Project Member Reported by hush@chromium.org, May 21 2016

Issue description

WebView version: 52.0.2743.1

Steps to reproduce:
1. enable webview multiprocess in dev options
2. open WebView Browser Tester app
3. go to www.google.com by typing in the address bar
4. go to www.test.com by typing in the address bar
5. blank page (if not, repeat 3-4). You can still see the scrollbar on the sides, and are able to scroll around.
6. the web page in dev tools shows up correctly

Nothing interesting is seen in logs. But I attached them anyway.

A note on attempts to bisects:
it's hard, because previously this issue was masked by another issue which was fixed only recently. (crbug.com/612365)

It works on m51.0.2704.28. So not a regression.
 
blank.txt
39.7 KB View Download

Comment 1 by hush@chromium.org, May 21 2016

Cc: boliu@chromium.org

Comment 2 Deleted

Comment 3 by hush@chromium.org, May 24 2016

synchronous_compositor_proxy still get HW swap buffers when it is stuck in the blank page state.

Comment 4 by boliu@chromium.org, May 31 2016

Labels: -Type-Bug -Pri-3 M-52 OS-Android Pri-1 Type-Bug-Regression
> It works on m51.0.2704.28. So not a regression.

You mean it *is* a regression?

> synchronous_compositor_proxy still get HW swap buffers when it is stuck in the blank page state.

Yeah but which one..?

Does this happen on the instrumentation shell? You can bisect that one
Project Member

Comment 5 by sheriffbot@chromium.org, Jun 1 2016

Labels: -M-52 M-53 MovedFrom-52
Moving this nonessential bug to the next milestone.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Project Member

Comment 7 by bugdroid1@chromium.org, Jun 8 2016

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/90144532ec5fc69209a72fdb7561704dec1c3ced

commit 90144532ec5fc69209a72fdb7561704dec1c3ced
Author: hush <hush@chromium.org>
Date: Wed Jun 08 02:09:48 2016

Android WebView: Always send memory policy from Browser to Renderer.

Early out on the Browser side does not work because the IPC message send could
succeed even if the output surface in question is not yet bound to client and
registered with the SynchronousCompositorRegistry.

BUG= 613781 

Review-Url: https://codereview.chromium.org/2035993003
Cr-Commit-Position: refs/heads/master@{#398460}

[modify] https://crrev.com/90144532ec5fc69209a72fdb7561704dec1c3ced/content/renderer/android/synchronous_compositor_output_surface.cc

Comment 8 by boliu@chromium.org, Jun 8 2016

#7 probably should be merged to m52 as well, probably affects single process as well
Verified on latest M53 webview /Nexus 6/Latest N build

Comment 10 by hush@chromium.org, Jun 29 2016

Status: Fixed (was: Assigned)

Comment 11 by boliu@chromium.org, Aug 22 2016

Cc: hush@chromium.org
 Issue 639906  has been merged into this issue.

Sign in to add a comment