Revert of Pass per-frame task runners to Workers (when possible)

Revert of Pass per-frame task runners to Workers (when possible) (patchset #5 id:100001 of https://codereview.chromium.org/2163983004/ )

Reason for revert:
Suspected for multiple failures in `WebKit Linux Leak` since
https://build.chromium.org/p/chromium.webkit/builders/WebKit%20Linux%20Leak/builds/21436

e.g. 

http/tests/serviceworker/foreign-fetch-workers.html
fast/workers/worker-document-leak.html
+ 7 more

errors like

10:21:04.195 21200 worker/1 http/tests/serviceworker/foreign-fetch-workers.html leaked
10:21:04.196 21133 [14636/39978] http/tests/serviceworker/foreign-fetch-workers.html failed unexpectedly (leak detected: ({"numberOfLiveActiveDOMObjects":[2,4],"numberOfLiveDocuments":[1,3],"numberOfLiveNodes":[4,28],"numberOfLiveResources":[0,2]}))
10:21:04.195 21200 worker/1 http/tests/serviceworker/foreign-fetch-workers.html failed:
10:21:04.195 21200 worker/1  leak detected: ({"numberOfLiveActiveDOMObjects":[2,4],"numberOfLiveDocuments":[1,3],"numberOfLiveNodes":[4,28],"numberOfLiveResources":[0,2]})


Original issue's description:
> Pass per-frame task runners to Workers (when possible)
> 
> - For in-process workers (i.e. dedicated/compositor workers): always use
>   the associated document's task runners
> - For out-of-process workers (i.e. service/shared workers): keep using the
>   default task runner of the main thread, but via TaskRunnerHelper so
>   we could still start using different task runners for different tasks
>   (e.g. loading vs timer) if we want.
> 
> BUG=627034
> 
> Committed: https://crrev.com/66b07a326160fed57046fbb454f424a302d4cc6b
> Cr-Commit-Position: refs/heads/master@{#408652}

TBR=skyostil@chromium.org,hiroshige@chromium.org,haraken@chromium.org,nhiroki@chromium.org,kinuko@chromium.org
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=627034

[tapted, 2016-08-01 02:43:26]

The CQ bit was checked by tapted@chromium.org

[tapted, 2016-08-01 02:43:27]

Created Revert of Pass per-frame task runners to Workers (when possible)

[commit-bot: I haz the power, 2016-08-01 02:43:37]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[haraken, 2016-08-01 02:44:56]

LGTM

[commit-bot: I haz the power, 2016-08-01 02:45:07]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-08-01 02:45:08]

Try jobs failed on following builders:
  ios-device on master.tryserver.chromium.mac (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.mac/builders/ios-device/builds...)
  ios-simulator on master.tryserver.chromium.mac (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.mac/builders/ios-simulator/bui...)
  mac_chromium_rel_ng on master.tryserver.chromium.mac (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.mac/builders/mac_chromium_rel_...)

[tapted, 2016-08-01 02:47:22]

On 2016/08/01 02:45:08, commit-bot: I haz the power wrote:
> Try jobs failed on following builders:
>   ios-device on master.tryserver.chromium.mac (JOB_FAILED,
>
http://build.chromium.org/p/tryserver.chromium.mac/builders/ios-device/builds...)
>   ios-simulator on master.tryserver.chromium.mac (JOB_FAILED,
>
http://build.chromium.org/p/tryserver.chromium.mac/builders/ios-simulator/bui...)
>   mac_chromium_rel_ng on master.tryserver.chromium.mac (JOB_FAILED,
>
http://build.chromium.org/p/tryserver.chromium.mac/builders/mac_chromium_rel_...)

doh - conflicts with r408886, but I should be able to resolve

[tapted, 2016-08-01 02:56:27]

The CQ bit was checked by tapted@chromium.org

[tapted, 2016-08-01 02:56:28]

The patchset sent to the CQ was uploaded after l-g-t-m from haraken@chromium.org
Link to the patchset: https://codereview.chromium.org/2196133002/#ps60003
(title: "rebase for conflict with r408886")

[commit-bot: I haz the power, 2016-08-01 02:56:40]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-08-01 03:04:53]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-08-01 03:04:54]

Try jobs failed on following builders:
  cast_shell_android on master.tryserver.chromium.android (JOB_FAILED,
https://build.chromium.org/p/tryserver.chromium.android/builders/cast_shell_a...)

[tapted, 2016-08-01 05:31:51]

The CQ bit was checked by tapted@chromium.org

[tapted, 2016-08-01 05:31:51]

The patchset sent to the CQ was uploaded after l-g-t-m from haraken@chromium.org
Link to the patchset: https://codereview.chromium.org/2196133002/#ps190001
(title: "fix merge")

[commit-bot: I haz the power, 2016-08-01 05:32:04]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-08-01 05:40:37]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-08-01 05:40:38]

Try jobs failed on following builders:
  cast_shell_android on master.tryserver.chromium.android (JOB_FAILED,
https://build.chromium.org/p/tryserver.chromium.android/builders/cast_shell_a...)

[tapted, 2016-08-01 06:17:11]

The CQ bit was checked by tapted@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2016-08-01 06:17:29]

Dry run: CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-08-01 06:26:06]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-08-01 06:26:06]

Dry run: Try jobs failed on following builders:
  linux_chromium_chromeos_ozone_rel_ng on master.tryserver.chromium.linux
(JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)

[tapted, 2016-08-01 06:52:41]

The CQ bit was checked by tapted@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2016-08-01 06:52:59]

Dry run: CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[tapted, 2016-08-01 06:55:00]

Wow - so this CL (r408652) conflicts with r408863 AND r408886 (yuck). Resolving
the conflicts with r408886 is mechanical, but r408863 is not. Trying a dry run
with patchset 5 now, but I don't really like it. kinuko@ are you around to take
this over and possibly work on a fix for the leaks, or revert the CL?

[commit-bot: I haz the power, 2016-08-01 07:03:24]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-08-01 07:03:25]

Dry run: Try jobs failed on following builders:
  cast_shell_android on master.tryserver.chromium.android (JOB_FAILED,
https://build.chromium.org/p/tryserver.chromium.android/builders/cast_shell_a...)
  linux_chromium_compile_dbg_ng on master.tryserver.chromium.linux (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)

[tzik, 2016-08-01 07:20:51]

On 2016/08/01 06:55:00, tapted wrote:
> Wow - so this CL (r408652) conflicts with r408863 AND r408886 (yuck).
Resolving
> the conflicts with r408886 is mechanical, but r408863 is not. Trying a dry run
> with patchset 5 now, but I don't really like it. kinuko@ are you around to
take
> this over and possibly work on a fix for the leaks, or revert the CL?

Another try for revert is getting green. Can I land it?
https://codereview.chromium.org/2199633002/

[haraken, 2016-08-01 07:22:13]

On 2016/08/01 07:20:51, tzik wrote:
> On 2016/08/01 06:55:00, tapted wrote:
> > Wow - so this CL (r408652) conflicts with r408863 AND r408886 (yuck).
> Resolving
> > the conflicts with r408886 is mechanical, but r408863 is not. Trying a dry
run
> > with patchset 5 now, but I don't really like it. kinuko@ are you around to
> take
> > this over and possibly work on a fix for the leaks, or revert the CL?
> 
> Another try for revert is getting green. Can I land it?
> https://codereview.chromium.org/2199633002/

I think yes.

[tapted, 2016-08-01 07:22:43]

On 2016/08/01 07:20:51, tzik wrote:
> On 2016/08/01 06:55:00, tapted wrote:
> > Wow - so this CL (r408652) conflicts with r408863 AND r408886 (yuck).
> Resolving
> > the conflicts with r408886 is mechanical, but r408863 is not. Trying a dry
run
> > with patchset 5 now, but I don't really like it. kinuko@ are you around to
> take
> > this over and possibly work on a fix for the leaks, or revert the CL?
> 
> Another try for revert is getting green. Can I land it?
> https://codereview.chromium.org/2199633002/

awesome: go for it :)