Closed
Bug 409735
Opened 17 years ago
Closed 17 years ago
XPConnect initialized twice
Categories
(Core :: XPConnect, defect, P2)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: sayrer, Unassigned)
Details
Attachments
(1 file)
|
4.63 KB,
text/plain
|
Details |
When running |make check| in a fresh checkout on OS X 10.5, XPConnect is initialized twice: once before component registration, and once after. This bug manifests as a Cycle Collector fault.
|
||
Updated•17 years ago
|
Flags: blocking1.9?
|
Reporter | |
Comment 1•17 years ago
|
||
I added an assertion in xpcModuleCtor to check for this. I always hit it eventually, even if I remove components that trigger it.
Actually, I don't think this should be blocking as it doesn't affect anything other than |make check| apparently? This does mean that we can't do any leak testing during |make check| though.
Benjamin, got any ideas here?
Flags: blocking1.9+ → blocking1.9-
|
||
Comment 4•17 years ago
|
||
It would be useful to get a stack for the first initialization as well... I can't think of a reason this would happen offhand, unless component registration was being cleared and reloaded in an odd order.
|
|
Reporter | |
Comment 5•17 years ago
|
||
I can't get this to happen anymore.
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•