[Webkit-unassigned] [Bug 29193] [chromium] Need to prevent Javascript sleeps in unload handlers

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Tue Sep 15 08:48:20 PDT 2009


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





--- Comment #9 from John Abd-El-Malek <jam at chromium.org>  2009-09-15 08:48:14 PDT ---
(In reply to comment #8)
> Another wonky thing is that you leak this powerful function that calls
> v8::V8::TerminateExecution() to the page.  I'm not entirely sure what evil
> things the page might do with that function, but it seems like a bad idea.

Do you mean indirectly leak by calling getTime 1K times in an unload handler? 
The page can't do anything that will call this function otherwise, since the
only pointer to it is in the closure.

Re getTime.toString showing different results.  I think this is pretty minor,
especially compared to the problems that this solves (check out the chromium
bug link for comments on how big the problem is, and other drastic changes that
people wanted to do to prevent it).  It won't be possible to do this with no
side effects unless we have V8 changes, which the V8 team doesn't think is
necessary.  They are happy with this approach (Mads reviewed it).

This is a stop-gap measure until we implement <a ping> and evangelize it.

-- 
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