Oilpan: non-eagerly trace HTML element stack records.

Oilpan: non-eagerly trace HTML element stack records.

For some parses, the ElementRecord chains kept by the HTML element parse
stack might end up very long, requiring corresponding amounts of call
stack when being traced eagerly.

Use the marking stack instead for these objects, as is done for the
ContainerNodes these record objects refer to.

R=haraken
BUG=420515
Committed: https://src.chromium.org/viewvc/blink?view=rev&revision=187808

[sof, 2014-12-31 07:36:30]

sigbjornf@opera.com changed reviewers:
+ oilpan-reviews@chromium.org

[sof, 2014-12-31 07:36:30]

Please take a look.

Trace depth assert triggered on the bots,


https://storage.googleapis.com/chromium-layout-test-archives/WebKit_Win_Oilpa...

(I bet it has been investigated already, but one wonders if the parser can keep
the reachable ContainerNodes as traceable Member<>s only. That way the
HTMLElementStack and its objects could remain off-heap and maintain raw
pointers. Not entirely tidy, but could avoid heap allocation stress on a bunch
of tests.)

[haraken, 2014-12-31 13:01:35]

LGTM

[sof, 2014-12-31 13:24:06]

The CQ bit was checked by sigbjornf@opera.com

[commit-bot: I haz the power, 2014-12-31 13:24:31]

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

[commit-bot: I haz the power, 2014-12-31 14:46:51]

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