[Webkit-unassigned] [Bug 62292] Worker object may be garbage collected even if it has message handlers

[bugzilla-daemon at webkit.org]

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





--- Comment #4 from Dmitry Titov <dimich at chromium.org>  2011-06-08 12:16:22 PST ---
(In reply to comment #3)
> Doesn't fast/workers/worker-gc.html aim at testing just this? I wonder what's so different in Yury's example.

During test in worker-gc.html, the Worker always has 'pending activity' in the form of a message being sent and replied. 

In the Yury.s example, I would expect the "ping" message to be delivered to the worker context, and if the worker context replies with another message from its onmessage handler, it would be delivered back and appended to console log. After that, if there is no pending activity in the worker context (no timers, xhrs, database requests, file operations) - the worker becomes 'unprotected' (as spec says) in a sense that it can not fire any new events and thus can be GC'ed safely, together with its event handlers.

However, if in this example the worker context replies back but the even handler is not firing because it was GC'ed, it's a bug.

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