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

Issue 739499 link

Starred by 4 users

Issue metadata

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



Sign in to add a comment

Display::SurfaceDiscarded doesn't do the right thing?

Project Member Reported by fsam...@chromium.org, Jul 5 2017

Issue description

When we discard a surface, we call Display::SurfaceDiscarded which, in turn calls SurfaceAggregator::ReturnResources(surface_id) which tries to return resources to the child. The CompositorFrameSinkSupport is likely being destroyed at that point, and so it might've already lost its connection and cannot return resources. Is this a bug?

We only drop a CompositorFrameSinkSupport on gpu restart right? In that case, does the renderer already through away all resource bookkeeping?
 
Owner: danakj@chromium.org
I'm not sure I'm familiar enough to own this or answer any of your questions :) I can only comment as to why I added OnSurfaceDestroyed - for that, see discussion on this patch: https://codereview.chromium.org/2918883002/.
Owner: fsam...@chromium.org
Cc: samans@chromium.org
Status: WontFix (was: Assigned)
Marking as WontFix as Saman is working on a better solution.

Sign in to add a comment