Closed Bug 403667 Opened 17 years ago Closed 16 years ago

###!!! ASSERTION: URI mapped to two different specs?

Categories

(Core :: XPCOM, defect)

defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 180909

People

(Reporter: cbook, Unassigned)

Details

(Keywords: assertion)

###!!! ASSERTION: URI mapped to two different specs?: 'uriMapEntry->mDocMapEn == nsnull', file c:/work/mozilla/builds/1.9.0-trace-malloc/mozilla/xpcom/io/astLoadFile.cpp, line 420

Steps to reproduce:
Start Trunk
Go to Options -> Applications
Quit Firefox

Restart Firefox
Go again to options (the Applications Tab should be loaded)
-> Assertion
Keywords: assertion
Product: Firefox → Core
QA Contact: general → general
I get this whenever pulling up the Preferences dialog on Linux on recent trunk builds. Also get "ASSERTION: redundant multiplexed document?".. not sure if it's a related issue.
A clean Mac compiled trunk Thunderbird debug build version 3.0a1pre
(2008040301) outputs the following on startup:

###!!! ASSERTION: URI mapped to two different specs?: 'uriMapEntry->mDocMapEntry == nsnull', file /Users/skywalker/Desktop/Mozilla/cvs/mozilla/xpcom/io/nsFastLoadFile.cpp, line 420
Blocks: tb-noise
Comment #2 no longer occurs with Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1b1pre) Gecko/20080910155414 Shredder/3.0b1pre
No longer blocks: tb-noise
Timeless, somehow related to your bug 180909?
Component: General → XPCOM
OS: Windows XP → All
QA Contact: general → xpcom
Hardware: PC → All
This assertion has come back again when starting up a compiled debug TB with Lightning enabled, on Mac 10.5.5.
Blocks: tb-noise
yeah, we don't need more than one bug for this. and since i'm hitting it again and have the oldest bug on record for it, i'd sooner use that one :)
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → DUPLICATE
Timeless, if your bug is still valid then this one isn't a dupe. I did the steps from comment 0 and it doesn't assert with a latest Shiretoko or Minefield debug build. Finally I don't have the stack here to be 100% sure.
You need to log in before you can comment on or make changes to this bug.