New issue
Advanced search Search tips

Issue 896253 link

Starred by 1 user
Status: WontFix
Owner: ----
Closed: Oct 17
Cc:
sullivan@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

1%-40.9% regression in avg_surface_fps,frame_times,mean_frame_time_renderer_compositor,thread_raster_cpu_time_per_frame at 599534:599537

Project Member Reported by 42576172...@developer.gserviceaccount.com, Oct 17 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Oct 17 

All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=896253

(For debugging:) Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?sid=92969f1f10b1d5ac218177f154bc42422bb7fe7b11749bf516075ebbed603827


Bot(s) for this bug's original alert(s):

android-nexus5x-perf

rendering.mobile - Benchmark documentation link:
  https://bit.ly/rendering-benchmarks
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Oct 17 

📍 Couldn't reproduce a difference.
https://pinpoint-dot-chromeperf.appspot.com/job/1499117ce40000

Comment 4 by sullivan@chromium.org, Oct 17

Status: WontFix (was: Untriaged)
This looks like some kind of hiccup, the metric is returning to previous values after an unexplained drop.
►

Sign in to add a comment