Closed
Bug 119038
Opened 24 years ago
Closed 24 years ago
Assertion: document demuxed from FastLoad file more than once?: 'entry->mNextSegmentOffset != 0' nsFastLoadFile.cpp#527
Categories
(Core :: XUL, defect)
Core
XUL
Tracking
()
RESOLVED
FIXED
People
(Reporter: timeless, Assigned: harishd)
Details
(Keywords: assertion)
Attachments
(3 files)
|
5.85 KB,
text/plain
|
Details | |
|
1.04 KB,
patch
|
Details | Diff | Splinter Review | |
|
1.93 KB,
patch
|
hjtoi-bugzilla
:
review+
brendan
:
superreview+
|
Details | Diff | Splinter Review |
I'll attach the stack trace and nspr log.
i accidentally let mozilla clobber my log leaving me with a shorter and less
interesting log, i'll try again later.
Comment 3•24 years ago
|
||
Oh, wait. Is this only FreeBSD? Is this the trunk? Does this happen on each
startup (or every second?).
Comment 4•24 years ago
|
||
OK, I'll answer my own question. In my opt. build [with a printf for the
assertion], I get this condition every second time I start the browser on
Linux.
I suspect that this may be [part of] the problem with window and pageload
regression on tinderboxen (see bug 119066).
Severity: normal → major
OS: FreeBSD → All
Comment 5•24 years ago
|
||
This applies to today's comm. builds on Mac and win32 as well.
Hardware: PC → All
ok, then i'm not going to keep ownership of this bug :) yes cvs tip.
Assignee: timeless → brendan
Comment 7•24 years ago
|
||
Zoiks. Does all become well if harishd's changes are backed out?
All this stuff is fragile, as the best hacks tend to be.
/be
Comment 8•24 years ago
|
||
> Does all become well if harishd's changes are backed out?
I'll answer in the opposite direction. A build pulled by date Jan 8 17:36 PST,
just before harishd's first batch of checkins, did not blow away XUL.mfasl on
every second startup (with that assertion showing). When I applied harishd's
first flight of checkins, at 17:37 PST, and rebuilt from the top, this was no
longer the case; XUL.mfasl would be blown away on every second startup with
that assertion.
(Sidenote: but for 1MB of bloat reduction and faster startup, these are the
kind of regressions I almost kinda like tracking down :-]).
Comment 9•24 years ago
|
||
harishd is loggin WillResume calls against Start/EndMuxedDocument (WillResume
calls SelectMuxedDocument), and comparing with and without his patch. I suspect
something in how WillResume is called changed.
/be
Comment 10•24 years ago
|
||
Harish is all over this, thanks to my WillResume suspicion.
/be
Assignee: brendan → harishd
| Assignee | ||
Comment 11•24 years ago
|
||
| Assignee | ||
Comment 12•24 years ago
|
||
Comment on attachment 64416 [details] [diff] [review]
patch v1.2 [ Removed default values from WillResumeParse() & WillInterruptParse() ]
r=heikki
Attachment #64416 -
Flags: review+
Comment 14•24 years ago
|
||
Comment on attachment 64416 [details] [diff] [review]
patch v1.2 [ Removed default values from WillResumeParse() & WillInterruptParse() ]
sr=brendan@mozilla.org
Attachment #64416 -
Flags: superreview+
| Assignee | ||
Comment 15•24 years ago
|
||
fixed.
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
Component: XP Toolkit/Widgets: XUL → XUL
QA Contact: jrgmorrison → xptoolkit.widgets
You need to log in
before you can comment on or make changes to this bug.
Description
•