New issue
Advanced search Search tips

Issue 876709 link

Starred by 2 users

Issue metadata

Status: Fixed
Owner:
Closed: Aug 28
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

3.6%-19.3% regression in rendering.mobile at 581549:583986

Project Member Reported by majidvp@chromium.org, Aug 22

Issue description

Most likely a duplicate of 875911
 
All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=876709

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


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

Android Nexus5 Perf
android-nexus5x-perf
Cc: yiyix@chromium.org
Owner: yiyix@chromium.org
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/1491ed91640000

FrameMetrics: Adding frame metrics analysis to LayerTreeHostImpl by yiyix@chromium.org
https://chromium.googlesource.com/chromium/src/+/808c1f33139afdc7d32b838938ed297a3f27f8f1
37.62 → 43.44 (+5.823)

Understanding performance regressions:
  http://g.co/ChromePerformanceRegressions
I will keep it beta to take some measurement, then i will revert it before stable cut for M69. 
Status: Fixed (was: Assigned)
The cl is reverted here: https://chromium-review.googlesource.com/c/chromium/src/+/1194685

closing the bug

Sign in to add a comment