Handle rejected promises better for workers.

Source/bindings/core/v8/WorkerScriptController.cpp

Index: Source/bindings/core/v8/WorkerScriptController.cpp
diff --git a/Source/bindings/core/v8/WorkerScriptController.cpp b/Source/bindings/core/v8/WorkerScriptController.cpp
index b0f4bb56c54aef3088768e914b0d73c007ab762a..bbd4bf7912058bcf822ab14ef5ff049894a51b5e 100644
--- a/Source/bindings/core/v8/WorkerScriptController.cpp
+++ b/Source/bindings/core/v8/WorkerScriptController.cpp
@@ -107,6 +107,7 @@ WorkerScriptController::WorkerScriptController(WorkerGlobalScope& workerGlobalSc
     , m_workerGlobalScope(workerGlobalScope)
     , m_executionForbidden(false)
     , m_executionScheduledToTerminate(false)
+    , m_rejectedPromises(RejectedPromises::create())
     , m_globalScopeExecutionState(0)
 {
     m_isolate = V8PerIsolateData::initialize();
@@ -140,6 +141,9 @@ private:
 
 WorkerScriptController::~WorkerScriptController()
 {
+    m_rejectedPromises->dispose();

[haraken, 2015/02/08 01:53:55]

Won't ~WorkerScriptController() be called in some destructor of an on-heap
object?

I guess it would be safe to call dispose() in WorkerGlobalScope::dispose().

[sof, 2015/02/08 06:57:39]

It is called from there; the OwnPtr<WorkerScriptController> is cleared via
clearScript().

+    m_rejectedPromises.clear();
+
     ThreadState::current()->removeInterruptor(m_interruptor.get());
 
     m_world->dispose();