Make Event RefCountedGarbageCollected and implement trace() methods to the Event hierarcy

Source/modules/device_orientation/DeviceMotionEvent.h

Index: Source/modules/device_orientation/DeviceMotionEvent.h
diff --git a/Source/modules/device_orientation/DeviceMotionEvent.h b/Source/modules/device_orientation/DeviceMotionEvent.h
index 6a638cae7da83a48e804594f946ac39a814bb785..ce19d5fb6403af6c04cac2b439e34a45fff75700 100644
--- a/Source/modules/device_orientation/DeviceMotionEvent.h
+++ b/Source/modules/device_orientation/DeviceMotionEvent.h
@@ -58,15 +58,16 @@ public:
 
     virtual const AtomicString& interfaceName() const OVERRIDE;
 
+    virtual void trace(Visitor*) OVERRIDE;
+
 private:
     DeviceMotionEvent();
     DeviceMotionEvent(const AtomicString& eventType, DeviceMotionData*);
 
-    RefPtrWillBePersistent<DeviceMotionData> m_deviceMotionData;
-
-    RefPtrWillBePersistent<DeviceAcceleration> m_acceleration;
-    RefPtrWillBePersistent<DeviceAcceleration> m_accelerationIncludingGravity;
-    RefPtrWillBePersistent<DeviceRotationRate> m_rotationRate;
+    RefPtrWillBeMember<DeviceMotionData> m_deviceMotionData;

[tkent, 2014/02/26 08:14:03]

I have a concern about changes like this.

After this change, applying real Oilpan types in modules/device_orientation
would not be a simple task.
* Need to consume time to distinguish between module-related and event-related.
* Need to introduce PersistentWillBeMember transition type.

[haraken, 2014/02/26 08:18:30]

Good point. The concern is valid. However, we cannot use persistent handles in
garbage-collected objects (because they will cause leaks).

Mads: Do you have any idea to address the issue?

+    RefPtrWillBeMember<DeviceAcceleration> m_acceleration;
+    RefPtrWillBeMember<DeviceAcceleration> m_accelerationIncludingGravity;
+    RefPtrWillBeMember<DeviceRotationRate> m_rotationRate;
 };
 
 DEFINE_TYPE_CASTS(DeviceMotionEvent, Event, event, event->interfaceName() == EventNames::DeviceMotionEvent, event.interfaceName() == EventNames::DeviceMotionEvent);