[Oilpan] Set stack limit using estimated sizes (Re-land)

Set the stack limit size based on estimated sizes.

To check if the stack memory has enough room for recursive
calls, we tried to allocate a large object and assumed the size.
This CL estimate the real thread stack limit using APIs.
On some platforms where such APIs do not work correctly,
we set the limit using the old algorithm.

---
This CL is re-land of https://codereview.chromium.org/910663002/
and https://codereview.chromium.org/927213002/.
Test was changed in another CL https://codereview.chromium.org/946483002/

BUG=420515, 457982
R=kouhei

Committed: https://src.chromium.org/viewvc/blink?view=rev&revision=190636

[peria, 2015-02-23 03:49:54]

PTL

[peria, 2015-02-23 03:50:11]

peria@chromium.org changed reviewers:
+ kouhei@chromium.org, oilpan-reviews@chromium.org

[peria, 2015-02-23 03:50:12]

PTL

[haraken, 2015-02-23 03:57:32]

LGTM

[peria, 2015-02-23 03:57:59]

The CQ bit was checked by peria@chromium.org

[commit-bot: I haz the power, 2015-02-23 03:58:17]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/943293002/20001

[kouhei (in TOK), 2015-02-23 04:10:43]

lgtm

[commit-bot: I haz the power, 2015-02-23 05:15:11]

Committed patchset #2 (id:20001) as
https://src.chromium.org/viewvc/blink?view=rev&revision=190636

[hiroshige, 2015-02-23 10:09:43]

Hi,
I'm suspecting this CL causes browser test failures.
See https://crbug.com/460868 for details.

[hiroshige, 2015-02-23 11:13:08]

A revert of this CL (patchset #2 id:20001) has been created in
https://codereview.chromium.org/953453003/ by hiroshige@chromium.org.

The reason for reverting is: Speculatively reverted due to failures in browser
test ExtensionPageCaptureApiTest.SaveAsMHTML.

BUG=460868.