Skip to content

Correct the first frame waiting logic and measurement #34867

New issue
New issue
Closed
Closed
Correct the first frame waiting logic and measurement#34867
Assignees
liyuqian
Labels
c: contributor-productivityTeam-specific productivity, code health, technical debt.c: performanceRelates to speed or footprint issues (see "perf:" labels)engineflutter/engine related. See also e: labels.frameworkflutter/packages/flutter repository. See also f: labels.
Milestone
December 2019
@liyuqian

Description

@liyuqian
liyuqian
opened on Jun 21, 2019

Many Flutter tests currently only wait for the UI thread to generate the layer tree of the first frame. It has caused problems like b/129875208, which causes #30463. It also makes our first frame benchmark inaccurate.

We should be able to solve this by utilizing Window.onReportTimings. We may need to modify it a little bit to report immediately on the first frame.

Metadata

Metadata

Assignees

Labels

c: contributor-productivityTeam-specific productivity, code health, technical debt.c: performanceRelates to speed or footprint issues (see "perf:" labels)engineflutter/engine related. See also e: labels.frameworkflutter/packages/flutter repository. See also f: labels.

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions