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

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


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

linux-release

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/12c9fec3f80000

📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/12c9fec3f80000

Enable frame pointers in linux.
By ajwong@chromium.org · Wed Nov 15 06:16:22 2017
chromium @ 9f966099a3d6f91c80016226fe9d33981f291689

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

The frame pointer change moves Linux release inline with other platforms (including ChromeOS) in a way that makes lots the runtime environment more easy to reason about. In particular, it'll allow us to gather much better memory stats from the field.  The tradeoff seems worth it. Also, I'm suspicious of this number as something of this sort should have seen an across-the-board perf hit rather than just a couple of isolated tests.

Lastly, the overall test numbers seem to be noisy. there was a huge cliff reduction that is multiple times larger than the file regression just now. 

Closing Won't Fix.