Open Bug 321199 Opened 20 years ago Updated 3 years ago

Should NS_InitXPCOM2/NS_InitXPCOM3 fail if you've already called one

Categories

(Core :: XPCOM, defect)

Product:
Core
Component:
XPCOM
Platform:
x86
Windows XP
Type:
defect

Tracking

()

People

(Reporter: timeless, Unassigned)

Details

someone helpfully added one of NS_InitXPCOM2/NS_InitXPCOM3 to an app that already had the other such that both were on the critical path. unfortunately SetMainThread fails if you call it a second time. Is this the behavior we want?
The behavior I want is that NS_InitXPCOM is not reentrant, but after NS_ShutdownXPCOM is called we can restart NS_InitXPCOM again. The second part is hard and the subject of several bugs already. The first part would be good to fix with a "xpcom is running" flag.
Status: UNCONFIRMED → NEW
Ever confirmed: true
mass reassigning to nobody.
Assignee: dougt → nobody
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.