[Webkit-unassigned] [Bug 72538] WebWorker threads can outlive the QApplication instance

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=72538





--- Comment #7 from Dmitry Titov <dimich at chromium.org>  2011-11-21 15:37:57 PST ---
I agree with Alexey here. There is all kinds of confirmations going between ScriptExecutionContext of the page and WorkerContext about shutdowns and terminations (not of the actual OS thread but of a message queue-based 'worker thread'). It should be enough to deallocate any resources allocated by port's implementation. "workerContextDestroyed" callback is the one I would probably look at.

We should not assume there is always going to be 1:1 correspondence between workers and OS threads. At least this is going to be port-specific. For example, Chromium can run workers in separate process and might need to manage threads/resources/shutdown sequence in a specific way there.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.