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

Issue 864499 link

Starred by 1 user

Issue metadata

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



Sign in to add a comment

100.2% regression in system_health.memory_desktop at 575228:575244

Project Member Reported by kraynov@chromium.org, Jul 17

Issue description

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

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


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/1497f22ea40000

Run font_service in-browser by drott@chromium.org
https://chromium.googlesource.com/chromium/src/+/b40906acf189f7764d0c75a173c2e03cc55eb620
8.951e+04 → 1.688e+05 (+7.931e+04)

Understanding performance regressions:
  http://g.co/ChromePerformanceRegressions
Components: Blink>Fonts
Status: WontFix (was: Assigned)
This a return to the values before the improvement in r572540 and the reland r572930. The improvement stems from running FontConfig out of process. However, doing that is a net negative, see issue 862553 and the blocked bugs of this issue for details.

Sign in to add a comment