[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 #9 from Yury Semikhatsky <yurys at chromium.org>  2011-06-09 00:14:02 PST ---
(In reply to comment #2)
> In your example, the worker object will be GC protected because there is an outstanding message. Once it's handled and acknowledged, and we also know that it hasn't triggered a timer or XHR inside the worker thread, it should be fine to collect the worker, because we know that it can't possibly be messaged again from either side.
> 
Does it mean that the worker object should stay alive while there is a pending activity in the corresponding worker context?

> Having handlers always GC protect the object would make it extremely likely to leak.
> 
Yeah, I understand that. As I see in current implementation tracking of pending activities in the worker context is supposed to address the issue.

> So, this is correct behavior. Do you have an example where the implementation doesn't match the design that I described above?
I posted my example, it looks like a bug in Chromium's implementation which appears after page refresh.

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