Revert of Add Resume logic of Purge+Suspend to TabManager.

Revert of Add Resume logic of Purge+Suspend to TabManager. (patchset #3 id:60001 of https://codereview.chromium.org/2462513002/ )

Reason for revert:
Reliably breaks Linux ChromiumOS Tests (1): https://build.chromium.org/p/chromium.chromiumos/builders/Linux%20ChromiumOS%20Tests%20%281%29/builds/28780 and Linux ChromiumOS Tests (dbg)(1): https://build.chromium.org/p/chromium.chromiumos/builders/Linux%20ChromiumOS%20Tests%20%28dbg%29%281%29/builds/19523

Original issue's description:
> Add Resume logic of Purge+Suspend to TabManager.
>
> - To avoid breaking web, we need to resume a backgrounded renderer that
>   was purged and suspended.
>   (A backgrounded renderer is suspended for 120seconds).
>   After resumed, the renderer is running for 10 seconds and is purged
>   and suspended again.
> - intent-to-implement-and-ship of background renderer's purge +
>   suspend is
>   https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/DK189tnM8l4
> - one of the documents attached in the above intent is
>   https://docs.google.com/document/d/1EgLimgxWK5DGhptnNVbEGSvVn6Q609ZJaBkLjEPRJvI/edit?usp=sharing
> - The feature is not enabled by default because
>   purge-and-suspend-time is 0.
>
> BUG=635419
>
> Committed: https://crrev.com/8241a62d2ba05a3c1d55d0e087986b637658892b
> Cr-Commit-Position: refs/heads/master@{#429222}

TBR=haraken@chromium.org,chrisha@chromium.org,tasak@google.com
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=635419
Committed: https://crrev.com/5af515953863b831c317fdbc70b8254e1784bff7
Cr-Commit-Position: refs/heads/master@{#429237}

[kjellander_chromium, 2016-11-02 08:12:27]

The CQ bit was checked by kjellander@chromium.org

[kjellander_chromium, 2016-11-02 08:12:28]

Created Revert of Add Resume logic of Purge+Suspend to TabManager.

[commit-bot: I haz the power, 2016-11-02 08:12:49]

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

[haraken, 2016-11-02 08:13:21]

LGTM to revert.

[commit-bot: I haz the power, 2016-11-02 08:13:52]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-11-02 08:15:46]

Description was changed from

==========
Revert of Add Resume logic of Purge+Suspend to TabManager. (patchset #3 id:60001
of https://codereview.chromium.org/2462513002/ )

Reason for revert:
Reliably breaks Linux ChromiumOS Tests (1):
https://build.chromium.org/p/chromium.chromiumos/builders/Linux%20ChromiumOS%...
and Linux ChromiumOS Tests (dbg)(1):
https://build.chromium.org/p/chromium.chromiumos/builders/Linux%20ChromiumOS%...

Original issue's description:
> Add Resume logic of Purge+Suspend to TabManager.
> 
> - To avoid breaking web, we need to resume a backgrounded renderer that
>   was purged and suspended.
>   (A backgrounded renderer is suspended for 120seconds).
>   After resumed, the renderer is running for 10 seconds and is purged
>   and suspended again.
> - intent-to-implement-and-ship of background renderer's purge +
>   suspend is
>   https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/DK189tnM8l4
> - one of the documents attached in the above intent is
>  
https://docs.google.com/document/d/1EgLimgxWK5DGhptnNVbEGSvVn6Q609ZJaBkLjEPRJ...
> - The feature is not enabled by default because
>   purge-and-suspend-time is 0.
> 
> BUG=635419
> 
> Committed: https://crrev.com/8241a62d2ba05a3c1d55d0e087986b637658892b
> Cr-Commit-Position: refs/heads/master@{#429222}

TBR=haraken@chromium.org,chrisha@chromium.org,tasak@google.com
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=635419
==========

to

==========
Revert of Add Resume logic of Purge+Suspend to TabManager. (patchset #3 id:60001
of https://codereview.chromium.org/2462513002/ )

Reason for revert:
Reliably breaks Linux ChromiumOS Tests (1):
https://build.chromium.org/p/chromium.chromiumos/builders/Linux%20ChromiumOS%...
and Linux ChromiumOS Tests (dbg)(1):
https://build.chromium.org/p/chromium.chromiumos/builders/Linux%20ChromiumOS%...

Original issue's description:
> Add Resume logic of Purge+Suspend to TabManager.
>
> - To avoid breaking web, we need to resume a backgrounded renderer that
>   was purged and suspended.
>   (A backgrounded renderer is suspended for 120seconds).
>   After resumed, the renderer is running for 10 seconds and is purged
>   and suspended again.
> - intent-to-implement-and-ship of background renderer's purge +
>   suspend is
>   https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/DK189tnM8l4
> - one of the documents attached in the above intent is
>  
https://docs.google.com/document/d/1EgLimgxWK5DGhptnNVbEGSvVn6Q609ZJaBkLjEPRJ...
> - The feature is not enabled by default because
>   purge-and-suspend-time is 0.
>
> BUG=635419
>
> Committed: https://crrev.com/8241a62d2ba05a3c1d55d0e087986b637658892b
> Cr-Commit-Position: refs/heads/master@{#429222}

TBR=haraken@chromium.org,chrisha@chromium.org,tasak@google.com
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=635419

Committed: https://crrev.com/5af515953863b831c317fdbc70b8254e1784bff7
Cr-Commit-Position: refs/heads/master@{#429237}
==========

[commit-bot: I haz the power, 2016-11-02 08:15:47]

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

[kjellander_chromium, 2016-11-02 08:22:42]

On 2016/11/02 08:15:47, commit-bot: I haz the power wrote:
> Patchset 1 (id:??) landed as
> https://crrev.com/5af515953863b831c317fdbc70b8254e1784bff7
> Cr-Commit-Position: refs/heads/master@{#429237}

FYI it also breaks several other bots:
https://build.chromium.org/p/chromium.win/builders/Win%207%20Tests%20x64%20%2...
https://build.chromium.org/p/chromium.mac/builders/Mac10.10%20Tests/builds/8568
https://build.chromium.org/p/chromium.mac/builders/Mac10.11%20Tests/builds/3138

I don't get why it doesn't fail this build though:
https://build.chromium.org/p/chromium.mac/builders/Mac10.9%20Tests/builds/31101
since
https://build.chromium.org/p/chromium.mac/builders/Mac10.9%20Tests/builds/31102
fails in a similar fashion. 
That is the only exception I can find, but other builds are failing at 429222 so
it cannot really be 429223 that is the culprit.

[tasak, 2016-11-02 09:09:49]

On 2016/11/02 08:22:42, kjellander_chromium wrote:
> On 2016/11/02 08:15:47, commit-bot: I haz the power wrote:
> > Patchset 1 (id:??) landed as
> > https://crrev.com/5af515953863b831c317fdbc70b8254e1784bff7
> > Cr-Commit-Position: refs/heads/master@{#429237}
> 
> FYI it also breaks several other bots:
>
https://build.chromium.org/p/chromium.win/builders/Win%207%20Tests%20x64%20%2...
>
https://build.chromium.org/p/chromium.mac/builders/Mac10.10%20Tests/builds/8568
>
https://build.chromium.org/p/chromium.mac/builders/Mac10.11%20Tests/builds/3138
> 
> I don't get why it doesn't fail this build though:
>
https://build.chromium.org/p/chromium.mac/builders/Mac10.9%20Tests/builds/31101
> since
>
https://build.chromium.org/p/chromium.mac/builders/Mac10.9%20Tests/builds/31102
> fails in a similar fashion. 
> That is the only exception I can find, but other builds are failing at 429222
so
> it cannot really be 429223 that is the culprit.

However,
https://build.chromium.org/p/chromium.chromiumos/builders/Linux%20ChromiumOS%...
is green.

[tasak, 2016-11-02 09:11:01]

On 2016/11/02 09:09:49, tasak wrote:
> On 2016/11/02 08:22:42, kjellander_chromium wrote:
> > On 2016/11/02 08:15:47, commit-bot: I haz the power wrote:
> > > Patchset 1 (id:??) landed as
> > > https://crrev.com/5af515953863b831c317fdbc70b8254e1784bff7
> > > Cr-Commit-Position: refs/heads/master@{#429237}
> > 
> > FYI it also breaks several other bots:
> >
>
https://build.chromium.org/p/chromium.win/builders/Win%207%20Tests%20x64%20%2...
> >
>
https://build.chromium.org/p/chromium.mac/builders/Mac10.10%20Tests/builds/8568
> >
>
https://build.chromium.org/p/chromium.mac/builders/Mac10.11%20Tests/builds/3138
> > 
> > I don't get why it doesn't fail this build though:
> >
>
https://build.chromium.org/p/chromium.mac/builders/Mac10.9%20Tests/builds/31101
> > since
> >
>
https://build.chromium.org/p/chromium.mac/builders/Mac10.9%20Tests/builds/31102
> > fails in a similar fashion. 
> > That is the only exception I can find, but other builds are failing at
429222
> so
> > it cannot really be 429223 that is the culprit.
> 
> However,
>
https://build.chromium.org/p/chromium.chromiumos/builders/Linux%20ChromiumOS%...
> is green.

As far as I understand, my patch is not enabled by default. So it is very
difficult to cause the issue.

[tasak, 2016-11-02 09:21:45]

A revert of this CL (patchset #1 id:1) has been created in
https://codereview.chromium.org/2471613003/ by tasak@google.com.

The reason for reverting is: Because the change added by the reverted patch is
not enabled by default.

.