New issue
Advanced search Search tips

Issue 862242 link

Starred by 1 user
Status: Fixed
Owner:
drott@chromium.org
Closed: Jul 17
Cc:
tdres...@chromium.org
drott@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression

Blocked on:
issue 862553


Sign in to add a comment

5.5%-8.9% regression in memory.desktop at 572922:572942

Project Member Reported by tdres...@chromium.org, Jul 10 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Jul 10 

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

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


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

linux-perf
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Jul 10

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/16c3dc34a40000

Move Blink Sandbox IPC to Mojo Calls by drott@chromium.org
https://chromium.googlesource.com/chromium/src/+/ac24004e3831e8a63a80c90cffbcbdd52b398e7c
1.233e+08 → 1.34e+08 (+1.07e+07)

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

Comment 4 by drott@chromium.org, Jul 13 

This has been partially addressed by the first commit on issue 862553, but will hopefully be further reduced by running in-process.

Comment 5 by drott@chromium.org, Jul 13

Blockedon: 862553

Comment 6 by drott@chromium.org, Jul 17

Status: Fixed (was: Assigned)
After r575234 which moves FontConfig access in-process again, I interpret the graphs to have been reduced again by a similar offset that r572930 introduced.
►

Sign in to add a comment