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

Issue 680184 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Jan 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 2
Type: Bug

Blocking:
issue 659227



Sign in to add a comment

Manage TLR surface references from GpuCompositorFrameSink

Project Member Reported by kylec...@chromium.org, Jan 11 2017

Issue description

If we could manage references from the TLR to display root surfaces then it would simplify things in the WS. FrameGenerator wouldn't need to handle adding and removing TLR references and DisplayCompositor wouldn't need to pass the TLR to DisplayCompositorClient.

This would also allow fixing removing the TLR reference to a display root before the compositor frame sink is destroyed. We remove references over the MojoCompositorFrameSink interface, so it's impossible to remove a reference after the interface connection is closed.
 
Labels: displaycompositor
TLR = Top Level Root, right? Thought I'd mention it so others reading this bug would know.
Owner: kylec...@chromium.org
Status: Assigned (was: Untriaged)
Is this fixed? Thanks!
Status: Fixed (was: Assigned)
Yep! It's now fixed.
Blocking:

Sign in to add a comment