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

Issue 846739 link

Starred by 3 users

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Unify the various frame counters

Project Member Reported by sadrul@chromium.org, May 25 2018

Issue description

There are currently several frame-counters:

 . CompositorFrameMetadata::frame_token
 . LayerTreeHost::source_frame_number_
 . frame_index in CompositorFrameSinkSupport

They are slightly different from each other, e.g. frame_token starts at 1, and a zero frame-token is invalid. source_frame_number_ starts at 0 (but is sometimes also negative, at least in tests). frame_index starts at 2 (not clear why).

These could all be unified.
 

Sign in to add a comment