Closed
Bug 326621
Opened 19 years ago
Closed 18 years ago
Navigating away after document.open triggers "ASSERTION: EndLoad called early" and "ASSERTION: More UnblockOnload() calls than BlockOnload() calls"
Categories
(Core :: DOM: Core & HTML, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: jruderman, Unassigned)
References
Details
(Keywords: assertion, testcase)
Attachments
(1 file)
62 bytes,
text/html
|
Details |
Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.9a1) Gecko/20060209 Firefox/1.6a1
Steps to reproduce:
1. Load testcase.
2. Click a bookmark in your bookmarks toolbar, drag a file from the desktop, etc.
###!!! ASSERTION: EndLoad called early: 'mWriteState == eNotWriting || mWriteState == ePendingClose || mWriteState == eDocumentClosed', file /Users/admin/trunk/mozilla/content/html/document/src/nsHTMLDocument.cpp, line 1031
###!!! ASSERTION: More UnblockOnload() calls than BlockOnload() calls; dropping call: 'Not Reached', file /Users/admin/trunk/mozilla/content/base/src/nsDocument.cpp, line 5249
Reporter | ||
Comment 1•19 years ago
|
||
Reporter | ||
Comment 2•19 years ago
|
||
Bug 332896 involves the same assertions.
![]() |
||
Comment 3•18 years ago
|
||
Jesse, do you still see this bug? I can't seem to reproduce over here....
Reporter | ||
Comment 4•18 years ago
|
||
I no longer see the assertion. I noticed that the back button doesn't work after navigating away from this testcase; I filed bug 376064 on that. Should this be retested once that bug is fixed?
![]() |
||
Comment 5•18 years ago
|
||
Probably... I dunno that that will get fixed any time soon, though. :( Especially since it's been a problem for at least two years, possibly more (I checked Jan 1, 2005 builds, which have the problem, then stopped).
Reporter | ||
Comment 6•18 years ago
|
||
Ok, I'll mark this as WFM and leave a note to myself to check for assertions once bug 376064 is fixed.
Status: NEW → RESOLVED
Closed: 18 years ago
Resolution: --- → WORKSFORME
Updated•6 years ago
|
Component: DOM → DOM: Core & HTML
You need to log in
before you can comment on or make changes to this bug.
Description
•