Closed Bug 513920 Opened 15 years ago Closed 15 years ago

Init IPC before necko

Categories

(Core :: IPC, defect)

Product:
Core
Component:
IPC
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED WONTFIX

People

(Reporter: jduell.mcbugs, Assigned: cjones)

References

Details

Or allow a way for necko init (in the child process) to bootstrap IPC.
The problem is that child processes "connect" over IPC to the parent process asynchronously. But there's really no point in doing that. Even the parent process connects synchronously (for the time being).
Pushed http://hg.mozilla.org/projects/electrolysis/rev/6d130d757d57
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
So this fix didn't work. A proper fix appears to be a fair amount of work re-jiggering our vs. Chromium's init sequencing. Since we're not even sure we're going to need a global necko protocol, and even if we do we can get it later, for now we're going to punt and just init necko IPC later.
Resolution: FIXED → WONTFIX
You need to log in before you can comment on or make changes to this bug.