Do not zero-initialize RawPtr.

Source/core/page/EventHandler.cpp

Index: Source/core/page/EventHandler.cpp
diff --git a/Source/core/page/EventHandler.cpp b/Source/core/page/EventHandler.cpp
index e0301a0034d9d5e7edd6564342e4facd19597c63..0d3b78445cfe89857c99644cd410a8cbcf794a97 100644
--- a/Source/core/page/EventHandler.cpp
+++ b/Source/core/page/EventHandler.cpp
@@ -3592,7 +3592,7 @@ bool EventHandler::handleTouchEvent(const PlatformTouchEvent& event)
     typedef HashSet<RefPtr<EventTarget> > EventTargetSet;
     struct {

[haraken, 2014/03/24 13:52:54]

Won't this be stack-allocated as well?

[Mads Ager (chromium), 2014/03/24 14:27:30]

Yes it will. I'm not sure what the plugin will say about this one, but using a
Member here and marking it STACK_ALLOCATED should be fine. Done.

         // The touches corresponding to the particular change state this struct instance represents.
-        RefPtrWillBeRawPtr<TouchList> m_touches;
+        RefPtrWillBeRawPtr<TouchList> m_touches = nullptr;
         // Set of targets involved in m_touches.
         EventTargetSet m_targets;
     } changedTouches[PlatformTouchPoint::TouchStateEnd];