Oilpan: Move ThreadableWebSocketChannelClientWrapper to Oilpan's heap

Source/core/dom/CrossThreadTask.h

Index: Source/core/dom/CrossThreadTask.h
diff --git a/Source/core/dom/CrossThreadTask.h b/Source/core/dom/CrossThreadTask.h
index 9902ebdcefdd38cedab485bf77ecd2c9608df52d..71622b493ef2b2fe23c5d1b6311e7bb79ea0800f 100644
--- a/Source/core/dom/CrossThreadTask.h
+++ b/Source/core/dom/CrossThreadTask.h
@@ -57,6 +57,10 @@ template<typename T> struct CrossThreadTaskTraits<PassOwnPtr<T> > {
     typedef PassOwnPtr<T> ParamType;
 };
 
+template<typename T> struct CrossThreadTaskTraits<CrossThreadPersistent<T> > {
+    typedef CrossThreadPersistent<T> ParamType;

[haraken, 2014/05/27 09:21:37]

This was the cause of the empty ASSERT error.

This template is expanded as follows:

class ExecutionContextTask {
  CrossThreadPersistent<ThreadableWebSocketChannelClientWrapper> param;
};

// This object is created in a worker thread.
class ThreadableWebSocketChannelClientWrapper : public
GarbageCollectedFinalized<ThreadableWebSocketChannelClientWrapper>{
  Vector<OwnPtr<ExecutionContextTask>> m_pendingTasks;
}

The problem happens in a case where the worker thread shuts down before flushing
m_pendingTasks. In that case, the worker thread calls collectAllGarbage() but it
cannot collect the ThreadableWebSocketChannelClientWrapper, because the
ThreadableWebSocketChannelClientWrapper and the CrossThreadPersistent are
referenced in a cycle.

I tried to explicitly clear m_pendingTasks before shutting down the worker
thread, but I found it's tricky. Also we won't want to add similar hacks to
other caller sites of ExecutionContextTask.

A better approach would be to move ExecutionContextTask to the heap and use a
Member instead of the CrossThreadPersistent. However, this requires a lot of
work.

As a short-term fix, I changed the CrossThreadPersistent to a RawPtr. This is
not safe in general but is OK in this particular case, because the tasks are
guaranteed to be executed in the same worker thread and thus
ThreadableWebSocketChannelClientWrapper is guaranteed to be alive while the
tasks are in the pending queue of the ThreadableWebSocketChannelClientWrapper.

What do you think?

+};
+
 template<typename P1, typename MP1>
 class CrossThreadTask1 : public ExecutionContextTask {
 public: