[Webkit-unassigned] [Bug 25394] CRASH in DocumentLoader::addResponse due to bad |this| pointer

Sun Apr 26 00:41:41 PDT 2009

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

fishd at chromium.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |ap at webkit.org,
                   |                            |levin at chromium.org

------- Comment #6 from fishd at chromium.org  2009-04-26 00:41 PDT -------
We could probably hack around this crash, but I think there is a bigger problem
at play here.  It seems like we should not allow any resource requests to begin
after the closeURL() call in FrameLoader::detachFromParent().

For reference:  The new resource requests are generated from within
stopAllLoaders.  There may be more than one way to achieve this, but the trick
I am using is to define an onabort handler on a XMLHttpRequest that I start in
my unload handler.  The onabort handler then starts another resource load. 
That resource load should not be allowed.  Or, maybe we should not even fire
event handlers at all after unload.  Thoughts?

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