[Webkit-unassigned] [Bug 32839] REGRESSION (r52446) - Crash starting an OutlivePage load

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Mon Dec 21 14:13:16 PST 2009


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





--- Comment #7 from Brady Eidson <beidson at apple.com>  2009-12-21 14:13:16 PST ---
(In reply to comment #5)
> (In reply to comment #4)
> > I'm assuming just keeping the document loader alive the same way r52446 keeps
> > the frame alive doesn't count as a solution?
> 
> It counts if it works.
> 
> Normally document loaders are closely tied to a document, so having a document
> loader around after the document is gone seems like it’s probably not a good
> thing. It might be better to have some sort of dummy document and a loader that
> goes along with that.

I think the Document->DocumentLoader relationship is pretty much as
set-in-stone as the Frame->FrameLoader relationship, and we should keep it that
way.

It seems like we'll be opening the door for more of these "ping" type loads in
the future, and it would be best to keep them as lightweight as possible.  So I
like this dummy Document/DocumentLoader idea going forward, as it would contain
the ping loads inside one lightweight context instead of spreading them out
over many heavyweight contexts (like keeping each full-blown DocumentLoader
alive)

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