Revert of [heap] Ensure progress when incrementally marking wrappers

Revert of [heap] Ensure progress when incrementally marking wrappers (patchset #3 id:60001 of https://codereview.chromium.org/2592403002/ )

Reason for revert:
This won't work because the finalization still checks whether both marking deques are empty, also calling into blink. So we never proceed there.

Original issue's description:
> [heap] Ensure progress when incrementally marking wrappers
> 
> The problem here is estimating the marking step size for wrapper tracing. If the
> steps are too small, we cannot keep up with the mutator creating new wrappers.
> The result is an endless stream of incremental marking steps, alternating v8 and
> wrappers tracing, without ever finalizing in a GC.
> 
> The mitigation here is to abort finding the fix point after 10 incremental
> iterations.
> 
> A proper solution would track newly created wrappers on the blink side during
> wrapper tracing. Will give this more thought after the holidays.
> 
> BUG=chromium:668164, chromium:468240
> 
> Review-Url: https://codereview.chromium.org/2592403002
> Cr-Commit-Position: refs/heads/master@{#41923}
> Committed: https://chromium.googlesource.com/v8/v8/+/a47417b89373c615f9256800cfc803d84ba58378

TBR=ulan@chromium.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=chromium:668164, chromium:468240
Review-Url: https://codereview.chromium.org/2602433002
Cr-Commit-Position: refs/heads/master@{#41924}
Committed: https://chromium.googlesource.com/v8/v8/+/73036fb6916e5b2d75db766d695ae7a45af138a4

[Michael Lippautz, 2016-12-22 15:07:21]

The CQ bit was checked by mlippautz@chromium.org

[Michael Lippautz, 2016-12-22 15:07:22]

Created Revert of [heap] Ensure progress when incrementally marking wrappers

[commit-bot: I haz the power, 2016-12-22 15:07:29]

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-12-22 15:07:36]

CQ is committing da patch.

Bot data: {"patchset_id": 1, "attempt_start_ts": 1482419241985010, "parent_rev":
"a47417b89373c615f9256800cfc803d84ba58378", "commit_rev":
"73036fb6916e5b2d75db766d695ae7a45af138a4"}

[commit-bot: I haz the power, 2016-12-22 15:07:40]

Description was changed from

==========
Revert of [heap] Ensure progress when incrementally marking wrappers (patchset
#3 id:60001 of https://codereview.chromium.org/2592403002/ )

Reason for revert:
This won't work because the finalization still checks whether both marking
deques are empty, also calling into blink. So we never proceed there.

Original issue's description:
> [heap] Ensure progress when incrementally marking wrappers
> 
> The problem here is estimating the marking step size for wrapper tracing. If
the
> steps are too small, we cannot keep up with the mutator creating new wrappers.
> The result is an endless stream of incremental marking steps, alternating v8
and
> wrappers tracing, without ever finalizing in a GC.
> 
> The mitigation here is to abort finding the fix point after 10 incremental
> iterations.
> 
> A proper solution would track newly created wrappers on the blink side during
> wrapper tracing. Will give this more thought after the holidays.
> 
> BUG=chromium:668164, chromium:468240
> 
> Review-Url: https://codereview.chromium.org/2592403002
> Cr-Commit-Position: refs/heads/master@{#41923}
> Committed:
https://chromium.googlesource.com/v8/v8/+/a47417b89373c615f9256800cfc803d84ba...

TBR=ulan@chromium.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=chromium:668164, chromium:468240
==========

to

==========
Revert of [heap] Ensure progress when incrementally marking wrappers (patchset
#3 id:60001 of https://codereview.chromium.org/2592403002/ )

Reason for revert:
This won't work because the finalization still checks whether both marking
deques are empty, also calling into blink. So we never proceed there.

Original issue's description:
> [heap] Ensure progress when incrementally marking wrappers
> 
> The problem here is estimating the marking step size for wrapper tracing. If
the
> steps are too small, we cannot keep up with the mutator creating new wrappers.
> The result is an endless stream of incremental marking steps, alternating v8
and
> wrappers tracing, without ever finalizing in a GC.
> 
> The mitigation here is to abort finding the fix point after 10 incremental
> iterations.
> 
> A proper solution would track newly created wrappers on the blink side during
> wrapper tracing. Will give this more thought after the holidays.
> 
> BUG=chromium:668164, chromium:468240
> 
> Review-Url: https://codereview.chromium.org/2592403002
> Cr-Commit-Position: refs/heads/master@{#41923}
> Committed:
https://chromium.googlesource.com/v8/v8/+/a47417b89373c615f9256800cfc803d84ba...

TBR=ulan@chromium.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=chromium:668164, chromium:468240

Review-Url: https://codereview.chromium.org/2602433002
Cr-Commit-Position: refs/heads/master@{#41924}
Committed:
https://chromium.googlesource.com/v8/v8/+/73036fb6916e5b2d75db766d695ae7a45af...
==========

[commit-bot: I haz the power, 2016-12-22 15:07:40]

Committed patchset #1 (id:1) as
https://chromium.googlesource.com/v8/v8/+/73036fb6916e5b2d75db766d695ae7a45af...