Oilpan: dispose ServiceWorker (and registration) objects earlier.

Source/modules/serviceworkers/ServiceWorkerRegistration.h

Index: Source/modules/serviceworkers/ServiceWorkerRegistration.h
diff --git a/Source/modules/serviceworkers/ServiceWorkerRegistration.h b/Source/modules/serviceworkers/ServiceWorkerRegistration.h
index 0cf67c255bc50426162cca7b14412622f83f4327..fb31a15d33a0f23fd7a5153fce9bbe7c1c9290c4 100644
--- a/Source/modules/serviceworkers/ServiceWorkerRegistration.h
+++ b/Source/modules/serviceworkers/ServiceWorkerRegistration.h
@@ -31,6 +31,7 @@ class ServiceWorkerRegistration final
     DEFINE_WRAPPERTYPEINFO();
     DEFINE_EVENT_TARGET_REFCOUNTING_WILL_BE_REMOVED(RefCountedGarbageCollected<ServiceWorkerRegistration>);
     USING_GARBAGE_COLLECTED_MIXIN(ServiceWorkerRegistration);
+    WILL_BE_USING_PRE_FINALIZER(ServiceWorkerRegistration, dispose);

[haraken, 2015/01/26 01:39:42]

Can we drop WILL_BE_, since ServiceWorkerRegistration is already on-heap in
non-oilpan builds?

[sof, 2015/01/26 06:21:41]

But it doesn't use lazy sweeping?

[haraken, 2015/01/26 06:29:03]

Conceptually, whether we should enable lazy sweeping or not should be orthogonal
with whether oilpan is enabled or disabled. (i.e., we might need to enable lazy
sweeping in non-oilpan builds at some point.) So I'd prefer dropping WILL_BE_
here.

 public:
     // EventTarget overrides.
     virtual const AtomicString& interfaceName() const override;
@@ -70,6 +71,8 @@ private:
     virtual bool hasPendingActivity() const override;
     virtual void stop() override;
 
+    void dispose();
+
     OwnPtr<WebServiceWorkerRegistration> m_outerRegistration;
     WebServiceWorkerProvider* m_provider;
     RefPtrWillBeMember<ServiceWorker> m_installing;