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

Issue 864490 link

Starred by 1 user
Status: WontFix
Owner:
thomasanderson@chromium.org
Closed: Jul 17
Cc:
thomasanderson@chromium.org
█ kraynov@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

1.6% regression in system_health.memory_desktop at 575372:575398

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

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

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

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


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

linux-perf
Project Member

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

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/12d0f00ea40000

Roll fontconfig to d1f48f11 by thomasanderson@chromium.org
https://chromium.googlesource.com/chromium/src/+/3ff47e60c5ce645973e57fc8dbe88b43d63edaf4
1.179e+08 → 1.2e+08 (+2.137e+06)

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

Comment 4 by thomasanderson@chromium.org, Jul 17

Status: WontFix (was: Assigned)
BULK EDIT

Original fontconfig roll introduced a bug:
https://chromium.googlesource.com/chromium/src/+/a0c1584a2fade0146b7cd3380abe42feda02ad7c

Subsequent fontconfig roll fixed the regression introduced in the previous roll:
https://chromium.googlesource.com/chromium/src/+/a0c1584a2fade0146b7cd3380abe42feda02ad7c

The graphs indicate a performance improvement on the original roll that introduced the bug, and a regression after.  These performance differences are expected due to the nature of the bug introduced and then fixed.
►

Sign in to add a comment