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

Issue 886851 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Last visit > 30 days ago
Closed: Sep 30
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

2.2% regression in memory.top_10_mobile at 590823:590876

Project Member Reported by alexclarke@chromium.org, Sep 19

Issue description

See the link to graphs below.
 
All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=886851

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


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

Android Nexus5 Perf

memory.top_10_mobile - Benchmark documentation link:
  None
Cc: fsam...@chromium.org
Owner: fsam...@chromium.org
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/149dd7c0e40000

DelegatedFrameHostAndroid: Fix Screen Capture by fsamuel@chromium.org
https://chromium.googlesource.com/chromium/src/+/36be926f766fe3f0cb231123e4b9e6b087aa27e0
1.813e+07 → 1.84e+07 (+2.772e+05)

Understanding performance regressions:
  http://g.co/ChromePerformanceRegressions

Benchmark documentation link:
  None
Status: WontFix (was: Assigned)
This was strictly a bug fix so I'm marking this as WontFix. If this caused a regression then we were outputting the wrong thing before.

Sign in to add a comment