[Webkit-unassigned] [Bug 39879] Geolocation activity started after frame has been disconnected can cause crash

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Tue Jun 8 07:49:55 PDT 2010


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





--- Comment #15 from Steve Block <steveblock at google.com>  2010-06-08 07:49:53 PST ---
The fix in Bug 39388 stops ongoing requests when the frame is disconnected. This was intended to avoid crashes in the bindings when callbacks are made after the frame has been disconnected. However, this only fixes the problem when the callback is made to the context of the Frame that owns the Geolocation object. A more general fix was made in Bug 40162, which aborts callbacks if the relevant ScriptExecutionContext or Frame has gone.

However, the fix in Bug 39388 is still required as other parts of the Geolocation machinery require the Frame. In this case, rather than simply dropping the requests, we should invoke the error callback with a new message.

We also need to do the same for new requests started after the frame has been detached, for the same reason. Patch coming.

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