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

Issue 870452 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Last visit > 30 days ago
Closed: Aug 22
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug

Blocking:
issue 857575



Sign in to add a comment

Don't send OnFirstSurfaceActivation to renderer processes

Project Member Reported by samans@chromium.org, Aug 2

Issue description

Once fallbacks are optional, avoid sending OnFirstSurfaceActivation messages to the renderer processes. i.e the following messages must not be sent when surface synchronization is enabled:

FrameMsg_FirstSurfaceActivation
BrowserPluginMsg_FirstSurfaceActivation


 
I'm not sure if that's quite right? I think the fallback should be set on cross-process navigation? Anytime the FrameSinkId changes, basically, right? That's a different IPC perhaps.
We still don't need an IPC. Whenever the FrameSinkId of the primary surface changes we can just update the fallback to be the first primary surface with the old FrameSinkId. ChildFrameCompositingHelper can automatically do this.
I like it!
Owner: ----
Status: Available (was: Assigned)
Owner: akaba@chromium.org
Status: Assigned (was: Available)
I think it's a good idea to work on this task after https://chromium-review.googlesource.com/c/chromium/src/+/1157404 is merged.

Description: Show this description
Won't the SurfaceRange grow unbounded if you never update the start SurfaceId?
kylechar: That's not really an issue anymore. We only need to update the start of the range to limit the earliest SurfaceId that can be embedded.
Also, we will not end up with a lot of surfaces even if the range is huge, because garbage collection will keep on removing old surfaces so the number of active surfaces per framesinkid is expected to be small.
Project Member

Comment 10 by bugdroid1@chromium.org, Aug 22

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

commit 383a1a1f7367e5ffdc717b304ab1f6f8c4cc2336
Author: akaba <akaba@google.com>
Date: Wed Aug 22 18:45:43 2018

Don't send OnFirstSurfaceActivation to renderer processes when surface sync is active.

This CL prevents the following messages from being sent to renderers when surface
sync is enabled:

FrameMsg_FirstSurfaceActivation
BrowserPluginMsg_FirstSurfaceActivation

This is because the extra IPC for updating is not needed anymore after fallback surfaces
are fully optional.

Bug:  870452 
Change-Id: I4a96fc759e230031d82ed4feb3c7c5697ca3c3c8
TBR: tsepez@chromium.org
Reviewed-on: https://chromium-review.googlesource.com/1183588
Commit-Queue: Andre Kaba <akaba@google.com>
Reviewed-by: Fady Samuel <fsamuel@chromium.org>
Cr-Commit-Position: refs/heads/master@{#585186}
[modify] https://crrev.com/383a1a1f7367e5ffdc717b304ab1f6f8c4cc2336/content/browser/browser_plugin/browser_plugin_guest.cc
[modify] https://crrev.com/383a1a1f7367e5ffdc717b304ab1f6f8c4cc2336/content/browser/frame_host/cross_process_frame_connector.cc

Status: Fixed (was: Assigned)

Sign in to add a comment