Oilpan: move node/element rare data objects to the heap.

Source/core/dom/Element.cpp

Index: Source/core/dom/Element.cpp
diff --git a/Source/core/dom/Element.cpp b/Source/core/dom/Element.cpp
index 8baa15a160791c998419753698f10698ec0ca75b..a9eb1539cd5134acf09ae5c1457e4dc3bdf65e8a 100644
--- a/Source/core/dom/Element.cpp
+++ b/Source/core/dom/Element.cpp
@@ -167,11 +167,10 @@ Element::~Element()
 {
     ASSERT(needsAttach());
 
+#if !ENABLE(OILPAN)
     if (hasRareData())
         elementRareData()->clearShadow();

[haraken, 2014/05/04 01:46:24]

I agree that you cannot access ElementRareData in ~Element(), but then who
clears the ElementShadow when the Element dies?

Probably do we need to move ElementShadow to the heap and change
ElementRareData::m_shadow to a Member? (However, at a first glance, it's not
clear how easy it is to move ElementShadow to the heap without making the Node
hierarchy traceable.)

-
-    if (hasActiveAnimations())
-        activeAnimations()->dispose();
+#endif
 
     if (isCustomElement())
         CustomElement::wasDestroyed(this);
@@ -1430,7 +1429,7 @@ void Element::detach(const AttachContext& context)
 
         if (ActiveAnimations* activeAnimations = data->activeAnimations()) {
             if (context.performingReattach) {
-                // FIXME: We call detach from withing style recalc, so compositingState is not up to date.
+                // FIXME: We call detach from within style recalc, so compositingState is not up to date.
                 // https://code.google.com/p/chromium/issues/detail?id=339847
                 DisableCompositingQueryAsserts disabler;