Closed
Bug 680413
Opened 13 years ago
Closed 13 years ago
Allow using child process message manager in chrome process
Categories
(Core :: IPC, defect)
Core
IPC
Tracking
()
RESOLVED
FIXED
People
(Reporter: smaug, Assigned: smaug)
References
Details
Attachments
(1 file)
16.47 KB,
patch
|
benjamin
:
review+
|
Details | Diff | Splinter 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.
Assignee | ||
Updated•13 years ago
|
Attachment #554382 -
Flags: review?(benjamin)
Comment 1•13 years ago
|
||
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.
Assignee | ||
Comment 2•13 years ago
|
||
If any frame mm script uses process mm, it would be hard to use the same code in-process mm.
Assignee | ||
Comment 3•13 years ago
|
||
So, the patch is about having consistent APIs.
Comment 4•13 years ago
|
||
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
Updated•13 years ago
|
Attachment #554382 -
Flags: review?(benjamin) → review+
Assignee | ||
Comment 5•13 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/9a72a10e8bb5
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Comment 6•13 years ago
|
||
> + PRBool isChrome = IsChromeProcess();
Should be bool.
You need to log in
before you can comment on or make changes to this bug.
Description
•