-
steveblock@google.com authored
Reviewed by Alexey Proskuryakov. Geolocation activity started after frame has been disconnected can cause crash https://bugs.webkit.org/show_bug.cgi?id=39879 New requests started after the Frame has been disconnected are ignored. We do not invoke the error callback as this would allow buggy or malicious pages to hose the CPU. Such a page could hold a reference to a Geolocation object from a since closed Page and register new requests from the error callback to create an infinite loop. Tests: fast/dom/Geolocation/disconnected-frame-already.html * page/Geolocation.cpp: 2010-08-13 Steve Block <steveblock@google.com> Reviewed by Alexey Proskuryakov. Geolocation activity started after frame has been disconnected can cause crash https://bugs.webkit.org/show_bug.cgi?id=39879 Added new tests to GTK skipped list. * fast/dom/Geolocation/disconnected-frame-already.html: Added. * fast/dom/Geolocation/disconnected-frame-already-expected.txt: Added. * fast/dom/Geolocation/script-tests/disconnected-frame-already.js: Added. * fast/dom/Geolocation/resources/disconnected-frame-already-inner1.html: Added. * fast/dom/Geolocation/resources/disconnected-frame-already-inner2.html: Added. * platform/gtk/Skipped: git-svn-id: http://svn.webkit.org/repository/webkit/trunk@65329 268f45cc-cd09-0410-ab3c-d52691b4dbfc
52ca7c02