[Webkit-unassigned] [Bug 18064] assert-fail in WebCore::FrameLoader::saveDocumentState (document is null)

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Wed Apr 2 11:22:31 PDT 2008


------- Comment #6 from julien.chaffraix at gmail.com  2008-04-02 11:22 PDT -------

the saveDocumentState does try to save frame's information but it is pointless
to save frame's information when they are not connected to a Document.
The core of the issue is how the frames are released. That's why the gtk port
is the only one concerned with this bug.
I have said that the Qt port would also fail but it is not longer the case. I
could not find exactly when it was fixed.
If you want to attack the real issue, I would advise you to have a look at
http://trac.webkit.org/projects/webkit/changeset/31521. This is the changeset
where Zecke has moved the portion of the code I had hold responsible for the
assertion failure (the code in FrameLoaderClient::detachedFromParent4()). The
other Qt commits from the same day should give an answer to how and when the
frame should be released to avoid both the assertion and a memory leak.

Configure bugmail: http://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.

More information about the webkit-unassigned mailing list