[Webkit-unassigned] [Bug 72538] WebWorker threads can outlive the QApplication instance
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Thu Nov 24 05:52:29 PST 2011
https://bugs.webkit.org/show_bug.cgi?id=72538
--- Comment #11 from Simon Hausmann <hausmann at webkit.org> 2011-11-24 05:52:29 PST ---
(In reply to comment #7)
> 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.
That's a good point, but even if workers are implemented as processes, don't you want those to terminate in a "controlled" way?
How does chromium enforce the termination of shared workers if for example I close the last window?
--
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
More information about the webkit-unassigned
mailing list