Closed Bug 14789 Opened 21 years ago Closed 20 years ago

assertion on exiting a page

Categories

(Core :: XPCOM, defect, P3)

x86
Windows NT
defect

Tracking

()

RESOLVED FIXED

People

(Reporter: karnaze, Assigned: dp)

Details

Any page asserts upon exiting it.

NTDLL! DbgBreakPoint@0 address 0x77f76148
nsDebug::Break(const char * 0x002bbe1c, int 439) line 155
nsDebug::Assertion(const char * 0x002bbe50, const char * 0x002bbe44, const char
* 0x002bbe1c, int 439) line 181 + 13 bytes
NS_ShutdownXPCOM(nsIServiceManager * 0x00b11580) line 439 + 31 bytes
main(int 1, char * * 0x00b115c0) line 139 + 10 bytes
mainCRTStartup() line 338 + 17 bytes
I was using viewer.exe
Status: NEW → ASSIGNED
NS_ASSERTION(cnt == 0, "Service Manager being held past XPCOM ");

mmh! got to see who is holding on to it. Might be the InitXPCOM() in raptor.
Target Milestone: M11
And got to check apprunner...
I see assert in apprunner if I open/close mail. If not no assert. I am looking
to see who is holding a reference.

Warren said he saw an assert too. Can you add where ?
I fixed the viewer one.
Status: ASSIGNED → RESOLVED
Closed: 20 years ago
Resolution: --- → FIXED
Summary: [CRASH] assertion on exiting a page → assertion on exiting a page
On first run js components have one of these. But that is a separate bug.
You need to log in before you can comment on or make changes to this bug.