frame->init() in the WebFrame constructor causes the InjectedBundlePageLoaderClient::didClearWindowObjectForFrame callback to be called with a reference to the WebFrame (at which point the WebFrame has not yet been adopted). We should fix this by moving the frame->init() call into the WebFrame::create method.
Created attachment 71238 [details] Move initializing the coreFrame into the WebFrame create method and out of the WebFrame constructor
Comment on attachment 71238 [details] Move initializing the coreFrame into the WebFrame create method and out of the WebFrame constructor r=me
Comment on attachment 71238 [details] Move initializing the coreFrame into the WebFrame create method and out of the WebFrame constructor Committed in r70148 http://trac.webkit.org/changeset/70148
http://trac.webkit.org/changeset/70148 might have broken Leopard Intel Release (Tests) The following tests are not passing: fast/workers/storage/interrupt-database-sync.html
(In reply to comment #4) > http://trac.webkit.org/changeset/70148 might have broken Leopard Intel Release (Tests) > The following tests are not passing: > fast/workers/storage/interrupt-database-sync.html Pretty unlikely, as we don't build WebKit2 stuff on Leopard.
http://trac.webkit.org/changeset/70173 might have broken SnowLeopard Intel Release (Tests) The following tests are not passing: http/tests/xmlhttprequest/origin-whitelisting-removal.html