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

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


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

chromium-rel-mac11

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/13c3eb54840000

The Pinpoint issue was fixed in https://github.com/catapult-project/catapult/issues/4185
I'll kick off a new bisect.

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/148e92bc840000

📍 Found significant differences after each of 2 commits.
https://pinpoint-dot-chromeperf.appspot.com/job/148e92bc840000

[bindings] Fix external memory accounting for SerializedScriptValue
By mlippautz@chromium.org · Wed Jan 17 14:37:16 2018
chromium @ da7248b830fcf503ab0fd0e4292c367bb5244ab9

DevTools: swapping from local frame to remote does not clear iframe contents in DOM domain.
By pfeldman@chromium.org · Wed Jan 17 17:49:25 2018
chromium @ 8f4c57cb0db64b9dc0c5aadcf50e0b1e457c612d

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

My change is a noop w/o inspector open.

My change can shift GC timing as we correctly report memory on the worker threads. In the regressed case I can see a MajorGC on a dedicated worker where we spend 44ms waiting for tasks to finish. Main thread wall time is 1.45ms. 

gab@ is currently looking into scheduling problems of V8 tasks in general and this might be related to the issues we have seen where we only make marginal progress on the main thread.

@Speed>Bisection : I can't seem to get anything out of pinpoint..

Clicking on " Analyze benchmark results"
@ https://pinpoint-dot-chromeperf.appspot.com/job/148e92bc840000
results in "HTTP response was too large: 50504270. The limit is: 33554432."

And I have no idea how I'm supposed to interpret the rest of the UI...

Related: https://github.com/catapult-project/catapult/issues/4168

+dtu

Thanks, looks like a bunch of tasks expired, filed a bug about the weird results: https://github.com/catapult-project/catapult/issues/4227