New issue
Advanced search Search tips

Issue 862298 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Jul 17
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression

Blocked on:
issue 862553



Sign in to add a comment

3%-7.6% regression in system_health.memory_desktop at 572922:572942

Project Member Reported by tdres...@chromium.org, Jul 10

Issue description

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

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


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

linux-perf
Cc: drott@chromium.org
Owner: drott@chromium.org
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/16a132b8a40000

Move Blink Sandbox IPC to Mojo Calls by drott@chromium.org
https://chromium.googlesource.com/chromium/src/+/ac24004e3831e8a63a80c90cffbcbdd52b398e7c
1.256e+08 → 1.347e+08 (+9.082e+06)

Understanding performance regressions:
  http://g.co/ChromePerformanceRegressions
Blockedon: 862553
Status: Fixed (was: Assigned)
After r575234 which moves FontConfig access in-process again, I interpret the graphs to have returned to values as before r572930.

Sign in to add a comment