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

Issue 868923 link

Starred by 1 user

Issue metadata

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

Blocked on:
issue 868925



Sign in to add a comment

SurfaceReference should store a parent SurfaceId and child SurfaceRange

Project Member Reported by akaba@google.com, Jul 30

Issue description

This will remove the need to update the references when a surface in the SurfaceRange activates and will enforce a stricter garbage collection scheme.
 
Blockedon: 868925
Currently SurfaceAggregator also calls GetLatestInFlightSurface. In order to minimize the number of times we call this method, I would rather not infer references inside of GarbageCollectSurfaces. Instead, we should update the references first, then finish DrawAndSwap, then garbage-collect.
@samans what do you mean by "update the references first".  Are you suggesting we keep the references to be  (surfaceId -> surfaceId) and infer references on activation?
If not, where do we infer the references other than GarbageCollectSurfaces?
Owner: akaba@chromium.org
Status: WontFix (was: Assigned)

Sign in to add a comment