Able to reproduce on Mac OS 10.12.5 using chrome latest stable #59.0.3071.86. This issue is not observed on Windows and Linux platform.

Bisect Information:
--------------------
Good build: 59.0.3068.1
Bad Build : 59.0.3070.0 

You are probably looking for a change made after 464024 (known good), but no later than 464025 (first known bad).

Change Log URL: 
https://chromium.googlesource.com/chromium/src/+log/5bc8d44f3ab226674d0dd2c52ef631d6d52dc464..78a049660074003b8e1e602b0e7783ca7f1f4ee0

From the above change log suspecting below change
Review-Url: https://codereview.chromium.org/2808273003

altimin@ - Could you please check whether this is caused with respect to your change, if not please help us in assigning it to the right owner. Since this is a latest regression observed on M-59 adding RB-Stable, Please feel free to remove if this is not the case.

Thanks!

Oops. This patch has been reverted on master: https://codereview.chromium.org/2850143003/, but managed to sneak into the release branch.

We should revert this upon release owners approval and I will write a postmortem.

Notwithstanding the above, thanks for the bug report. I'll look into it to make sure that everything will be alright when we reland this.

To clarify: the patch in question is known to be bad and was reverted in master due to test breakage. Most likely this problem affects not only extensions with setInterval, but many other use cases (e.g. telemetry failures causing the patch to be reverted in the first place).

Hereby I request permission to revert the patch in question in a release branch.

+amineer@, gkihumba@, cmasso@

Can you please confirm if this revert will be a safe merge? And we still need to determine if this is absolutely necessary - how many users are currently affected by this and is there any workaround solution or experiment that we can turn off?

Yes, this is going to be a safe merge. The main issue is that we don't know the full scope of the problem. Revert is the easiest and safest way.

Based on comments and stars, it's an urgent fix and safe merge as well. Approving merge for M59. Please go ahead and merge to branch 3071. We'll plan for a desktop respin middle of next week. 

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/6ccf3815953a4d8210a8809fe06e21b633cf8f15

commit 6ccf3815953a4d8210a8809fe06e21b633cf8f15
Author: Alexander Timin <altimin@chromium.org>
Date: Fri Jun 16 22:26:43 2017

Revert of [scheduler] Move some task types to suspendable task runner.

This reverts commit 78a049660074003b8e1e602b0e7783ca7f1f4ee0.

BUG= 733469 
TBR=altimin@chromium.org

Change-Id: I13ccff94000f70146d780da49268c2a30be74d70
Reviewed-on: https://chromium-review.googlesource.com/538696
Reviewed-by: Alexander Timin <altimin@chromium.org>
Cr-Commit-Position: refs/branch-heads/3071@{#797}
Cr-Branched-From: a106f0abbf69dad349d4aaf4bcc4f5d376dd2377-refs/heads/master@{#464641}
[modify] https://crrev.com/6ccf3815953a4d8210a8809fe06e21b633cf8f15/third_party/WebKit/Source/core/dom/TaskRunnerHelper.cpp

Verified this issue on Windows-10, Ubuntu 14.04 and Mac OS 10.12.5 using chrome latest stable #59.0.3071.109 and observed the cpu usage of dev tools didn't exceed more that 2% in chrome task manager. Confirming the fix is working as expected and adding TE-Verified label.

Thanks!

Deleted: Screen Shot 2017-06-20 at 2.12.58 PM.png 171 KB

	Screen Shot 2017-06-20 at 2.12.58 PM.png 171 KB View Download