Closed Bug 680413 Opened 9 years ago Closed 8 years ago

Allow using child process message manager in chrome process

Categories

(Core :: IPC, defect, major)

defect
Not set
major

Tracking

()

RESOLVED FIXED

People

(Reporter: smaug, Assigned: smaug)

References

Details

Attachments

(1 file)

Attached patch patchSplinter Review
...this way certain scripts can run also in non-e10s builds, and
in-process-frame-scripts can also use process mm.

Uploaded to try.
Attachment #554382 - Flags: review?(benjamin)
What needs this? I really want to discourage use of the process message manager and I don't want to take this unless the alternative is really messy code in some dependency.
If any frame mm script uses process mm, it would be hard to use the same code in-process mm.
So, the patch is about having consistent APIs.
Now that Session Restore is using the process message manager to handle data sent on unload, we need this patch to ensure that the same code works both when e10s is enabled and disabled.
Blocks: 516755
Severity: normal → major
Attachment #554382 - Flags: review?(benjamin) → review+
https://hg.mozilla.org/mozilla-central/rev/9a72a10e8bb5
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
> +  PRBool isChrome = IsChromeProcess();
Should be bool.
You need to log in before you can comment on or make changes to this bug.