Issue 840472 link

Starred by 1 user

Status:	WontFix
Owner:	khushals...@chromium.org
Closed:	Jun 2018
Cc:	enne@chromium.org khushals...@chromium.org
Components:	Internals>Compositing>OOP-Raster
EstimatedDays:	----
NextAction:	----
OS:	Android
Pri:	3
Type:	Bug

Regression in raster_cpu_time_per_frame for thread_times.oop_rasterization.key_mobile.

Project Member Reported by khushals...@chromium.org, May 7 2018

Chromium Commit Position range: 556097 - 556111

thread_raster_cpu_time_per_frame jumped from ~0.41 to ~0.46. Starting a bisect.

Project Member

Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8947163426622145600

Owner: khushals...@chromium.org
Status: Assigned (was: Untriaged)

Labels: -Pri-2 Pri-3

Looks like the bisect failed.

Project Member

Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8944242929974128192

Project Member

Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8943701459293591888

Status: WontFix (was: Assigned)

The bisect keeps failing on this.

►