New issue
Advanced search Search tips

Issue 866078 link

Starred by 1 user

Issue metadata

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



Sign in to add a comment

37.8% regression in system_health.memory_desktop at 575372:575398

Project Member Reported by npm@chromium.org, Jul 20

Issue description

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

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


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

linux-perf
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/1144de71a40000

Roll fontconfig to d1f48f11 by thomasanderson@chromium.org
https://chromium.googlesource.com/chromium/src/+/3ff47e60c5ce645973e57fc8dbe88b43d63edaf4
1.88e+05 → 2.397e+05 (+5.174e+04)

Understanding performance regressions:
  http://g.co/ChromePerformanceRegressions
Status: WontFix (was: Assigned)
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