New issue
Advanced search Search tips

Issue 621231 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Jun 2016
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

WebView multiprocess: RVHChanged is not called when switches::kRendererProcessLimit == 2

Project Member Reported by hush@chromium.org, Jun 17 2016

Issue description

I found that WebContentsObserver::RVHChanged is not called when doing cross domain navigation, if I set kRendererProcessLimit to 2.
Don't know why yet.
This will mess up the compositor switch logic in the future when we support more than one render processes -- by which time the cross domain related code could be changed a lot


 

Comment 1 by boliu@chromium.org, Jun 20 2016

I tried updating the renderer process limit to 5 here: https://codereview.chromium.org/2083673002 applied on top of r400679

cross domain navigation works fine, but trace shows navigations aren't actually creating new renderer processes, so perhaps I'm missing something here

Comment 2 by boliu@chromium.org, Jun 20 2016

Ahh, the default policy is site instance per process, so it won't create a process for cross-domain navigations. You can change the policy to kSitePerProcess, then cross-domain naivgations will create a new renderer process. And it works fine for me

However, bad news is tracing doesn't seem work. After going through 3 renderer processes, I only see traces for th last one.

Comment 3 by hush@chromium.org, Jun 20 2016

Status: WontFix (was: Untriaged)
I forgot to change the number of renderer processes in the xml file accordingly.
So close it

Comment 4 by boliu@chromium.org, Jun 20 2016

hush told me he forgot the manifest change

also hush was navigating from URL bar rather than from clicking links, that of course does create new site instances, so don't need kSitePerProcess

Sign in to add a comment