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

Issue 884335 link

Starred by 1 user
Status: WontFix
Owner:
█ fsam...@chromium.org
Last visit > 30 days ago
Closed: Sep 18
Cc:
█ fsam...@chromium.org
npm@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

2% regression in memory.top_10_mobile at 590823:590876

Project Member Reported by npm@chromium.org, Sep 14 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Sep 14 

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

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


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

Android Nexus5 Perf

memory.top_10_mobile - Benchmark documentation link:
  None
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Sep 18

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/171abf95640000

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

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

Benchmark documentation link:
  None

Comment 4 by fsam...@chromium.org, Sep 18

Status: WontFix (was: Assigned)
Marking as won't fix. This is a strict bug fix and any performance regression is as a result of the wrong thing happening before: wrong device scale factor.
►

Sign in to add a comment