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

Issue 886694 link

Starred by 1 user
Status: Assigned
Owner:
thomasanderson@chromium.org
Cc:
thomasanderson@chromium.org
█ alexclarke@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

5.5% regression in memory.desktop at 592124:592185

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

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

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

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


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

linux-perf

memory.desktop - Benchmark documentation link:
  None
Project Member

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

Cc: thomasanderson@chromium.org
Owner: thomasanderson@chromium.org
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/1472013f640000

[Refresh] Fix tab hit area not extending to top of window on tiling WMs by thomasanderson@chromium.org
https://chromium.googlesource.com/chromium/src/+/e831694a4379d6ccd59196571c7a80d196fd4b28
4.699e+06 → 4.883e+06 (+1.837e+05)

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

Benchmark documentation link:
  None
►

Sign in to add a comment