Revert of Delay leak reporting until worker in-process proxies have been finalized.

Revert of Delay leak reporting until worker in-process proxies have been finalized. (patchset #4 id:60001 of https://codereview.chromium.org/2026993004/ )

Reason for revert:
Speculative revert, seems to have broken some content_browsertests. See the bug:
BUG=616714
Original issue's description:
> Delay leak reporting until worker in-process proxies have been finalized.
>
> If a document creates a number of workers, terminating these and having
> their destruction ripple all the way back to the in-process proxy objects
> isn't immediate. But something that needs to complete before the leak
> detector can initiate reporting -- an in-process proxy object maintains a
> strong reference to the document, and would generate a leak if not
> destructed and its garbage having been collected afterwards.
>
> Address the reliability of multi worker shutdown by maintaining a
> counter of how many in-process proxy objects are still alive and run
> GCs until it drops to zero. Do that at most two times around.
>
> For documents not creating any workers, monitoring this proxy count
> avoids having to perform a third GC, something that was conservatively
> done before to address worker shutdown (but not reliably.)
>
> R=haraken,kouhei
> BUG=589802
>
> Committed: https://crrev.com/19895c52589f189d6fdc563759c9872af2cbf86c
> Cr-Commit-Position: refs/heads/master@{#397333}

TBR=haraken@chromium.org,kouhei@chromium.org,sigbjornf@opera.com
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=589802
Committed: https://crrev.com/16130e2f74c3ccd998d782b16836caf3a7e96f95
Cr-Commit-Position: refs/heads/master@{#397355}

[vabr (Chromium), 2016-06-02 10:19:15]

The CQ bit was checked by vabr@chromium.org

[vabr (Chromium), 2016-06-02 10:19:15]

Created Revert of Delay leak reporting until worker in-process proxies have been
finalized.

[commit-bot: I haz the power, 2016-06-02 10:19:38]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/2030883003/1
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/2030883003/1

[commit-bot: I haz the power, 2016-06-02 10:20:11]

Description was changed from

==========
Revert of Delay leak reporting until worker in-process proxies have been
finalized. (patchset #4 id:60001 of https://codereview.chromium.org/2026993004/
)

Reason for revert:
Speculative revert, seems to have broken some content_browsertests. See the bug:
BUG=616714

Original issue's description:
> Delay leak reporting until worker in-process proxies have been finalized.
> 
> If a document creates a number of workers, terminating these and having
> their destruction ripple all the way back to the in-process proxy objects
> isn't immediate. But something that needs to complete before the leak
> detector can initiate reporting -- an in-process proxy object maintains a
> strong reference to the document, and would generate a leak if not
> destructed and its garbage having been collected afterwards.
> 
> Address the reliability of multi worker shutdown by maintaining a
> counter of how many in-process proxy objects are still alive and run
> GCs until it drops to zero. Do that at most two times around.
> 
> For documents not creating any workers, monitoring this proxy count
> avoids having to perform a third GC, something that was conservatively
> done before to address worker shutdown (but not reliably.)
> 
> R=haraken,kouhei
> BUG=589802
> 
> Committed: https://crrev.com/19895c52589f189d6fdc563759c9872af2cbf86c
> Cr-Commit-Position: refs/heads/master@{#397333}

TBR=haraken@chromium.org,kouhei@chromium.org,sigbjornf@opera.com
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=589802
==========

to

==========
Revert of Delay leak reporting until worker in-process proxies have been
finalized. (patchset #4 id:60001 of https://codereview.chromium.org/2026993004/
)

Reason for revert:
Speculative revert, seems to have broken some content_browsertests. See the bug:
BUG=616714

Original issue's description:
> Delay leak reporting until worker in-process proxies have been finalized.
> 
> If a document creates a number of workers, terminating these and having
> their destruction ripple all the way back to the in-process proxy objects
> isn't immediate. But something that needs to complete before the leak
> detector can initiate reporting -- an in-process proxy object maintains a
> strong reference to the document, and would generate a leak if not
> destructed and its garbage having been collected afterwards.
> 
> Address the reliability of multi worker shutdown by maintaining a
> counter of how many in-process proxy objects are still alive and run
> GCs until it drops to zero. Do that at most two times around.
> 
> For documents not creating any workers, monitoring this proxy count
> avoids having to perform a third GC, something that was conservatively
> done before to address worker shutdown (but not reliably.)
> 
> R=haraken,kouhei
> BUG=589802
> 
> Committed: https://crrev.com/19895c52589f189d6fdc563759c9872af2cbf86c
> Cr-Commit-Position: refs/heads/master@{#397333}

TBR=haraken@chromium.org,kouhei@chromium.org,sigbjornf@opera.com
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=589802
==========

[commit-bot: I haz the power, 2016-06-02 10:20:12]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-06-02 10:21:19]

Description was changed from

==========
Revert of Delay leak reporting until worker in-process proxies have been
finalized. (patchset #4 id:60001 of https://codereview.chromium.org/2026993004/
)

Reason for revert:
Speculative revert, seems to have broken some content_browsertests. See the bug:
BUG=616714

Original issue's description:
> Delay leak reporting until worker in-process proxies have been finalized.
> 
> If a document creates a number of workers, terminating these and having
> their destruction ripple all the way back to the in-process proxy objects
> isn't immediate. But something that needs to complete before the leak
> detector can initiate reporting -- an in-process proxy object maintains a
> strong reference to the document, and would generate a leak if not
> destructed and its garbage having been collected afterwards.
> 
> Address the reliability of multi worker shutdown by maintaining a
> counter of how many in-process proxy objects are still alive and run
> GCs until it drops to zero. Do that at most two times around.
> 
> For documents not creating any workers, monitoring this proxy count
> avoids having to perform a third GC, something that was conservatively
> done before to address worker shutdown (but not reliably.)
> 
> R=haraken,kouhei
> BUG=589802
> 
> Committed: https://crrev.com/19895c52589f189d6fdc563759c9872af2cbf86c
> Cr-Commit-Position: refs/heads/master@{#397333}

TBR=haraken@chromium.org,kouhei@chromium.org,sigbjornf@opera.com
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=589802
==========

to

==========
Revert of Delay leak reporting until worker in-process proxies have been
finalized. (patchset #4 id:60001 of https://codereview.chromium.org/2026993004/
)

Reason for revert:
Speculative revert, seems to have broken some content_browsertests. See the bug:
BUG=616714

Original issue's description:
> Delay leak reporting until worker in-process proxies have been finalized.
>
> If a document creates a number of workers, terminating these and having
> their destruction ripple all the way back to the in-process proxy objects
> isn't immediate. But something that needs to complete before the leak
> detector can initiate reporting -- an in-process proxy object maintains a
> strong reference to the document, and would generate a leak if not
> destructed and its garbage having been collected afterwards.
>
> Address the reliability of multi worker shutdown by maintaining a
> counter of how many in-process proxy objects are still alive and run
> GCs until it drops to zero. Do that at most two times around.
>
> For documents not creating any workers, monitoring this proxy count
> avoids having to perform a third GC, something that was conservatively
> done before to address worker shutdown (but not reliably.)
>
> R=haraken,kouhei
> BUG=589802
>
> Committed: https://crrev.com/19895c52589f189d6fdc563759c9872af2cbf86c
> Cr-Commit-Position: refs/heads/master@{#397333}

TBR=haraken@chromium.org,kouhei@chromium.org,sigbjornf@opera.com
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=589802

Committed: https://crrev.com/16130e2f74c3ccd998d782b16836caf3a7e96f95
Cr-Commit-Position: refs/heads/master@{#397355}
==========

[commit-bot: I haz the power, 2016-06-02 10:21:20]

Patchset 1 (id:??) landed as
https://crrev.com/16130e2f74c3ccd998d782b16836caf3a7e96f95
Cr-Commit-Position: refs/heads/master@{#397355}

[sof, 2016-06-02 10:54:08]

lgtm, thanks for the revert.

Unexpected that these unit tests should require an extra GC.

[haraken, 2016-06-02 10:57:02]

LGTM