Add basic skeletal code for socket process: - GeckoProcessType - empty top-level IPC - XPCOM init - etc
This bug will be focusing on creating SocketProcessHost and the corresponding top-level IPDL. SocketProcess will initialize white-listed XPCOM. JS and cycle collection are not allowed in this process.
Assignee: kechang → cyu
Summary: Skeletal code for socket process → Create SocketProcessHost and corresponding IPC interfaces
Whiteboard: [necko-triaged] → [necko-triaged] [SOCK-PROC-M1]
The socket process may be enabled by setting the envvar NECKO_DEDICATED_PROCESS=1. At the moment the socket process doesn't do anything. Following its launch, we sync preferences, then start up XPCOM. More features to follow.
Kershaw, as agreed the last week, reassiging to you.
Assignee: valentin.gosu → kershaw
Summary of changes: - Rename - Add comments to classes that bring socket process up - Fix review comments - Remove some unnecessary changes - Remove the compiler dependency of nsIOService and IPC headers - Launch socket process after user's pref is loaded
Attachment #8927741 - Attachment is obsolete: true
Comment on attachment 9003841 [details] Bug 1416623 - Part1: Socket Process startup machinery r=mayhemer Kris Maglione [:kmag] has approved the revision.
Comment on attachment 9003841 [details] Bug 1416623 - Part1: Socket Process startup machinery r=mayhemer Honza Bambas (:mayhemer) has approved the revision.
Status: NEW → RESOLVED
Last Resolved: 8 months ago
Resolution: --- → FIXED
Duplicate of this bug: 1430045
You need to log in before you can comment on or make changes to this bug.