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

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


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

mac

Assigning to mlippautz@chromium.org because this is the only CL in range:
[oilpan] Enable incremental marking buildflag

Includes incremental garbage collection infrastructure in regular
builds. Does not enable incremental marking at runtime!

Sheriffs:
- This CL may cause throughput regressions and is an attempt
  to collect a broad range of potential performance issues.
- Binary size regressions of up to 100kb are expected. The infra
  added here is the minimal base for any future incremental and
  concurrent marking changes. Long term we will save a bit of
  memory by removing trace methods.

Bug:  chromium:757440 
Change-Id: I61f4dca6cb1933a9f10416bc6641aae3e8794455
Reviewed-on: https://chromium-review.googlesource.com/1052108
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Commit-Queue: Michael Lippautz <mlippautz@chromium.org>
Cr-Commit-Position: refs/heads/master@{#557576}