Create a prototype to experiment with using content processes as add-on processes

RESOLVED FIXED

Status

Add-on SDK
General
P1
normal
RESOLVED FIXED
7 years ago
7 years ago

People

(Reporter: ejpbruel, Assigned: ejpbruel)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Assignee)

Description

7 years ago
Firefox currently supports creating a single content process through the use of the <browser> element. We have used this feature to experiment with using content processes as add-on processes, but to get a better feel for whether or not content processes are too expensive for this, we need to be able to create more than just one.
(Assignee)

Comment 1

7 years ago
I've written a patch for mozilla-central that checks if type="addon" for the<browser> elements. If so, it does not get the content process using ContentParent::getSingleton, but uses ContentParent::getAddon, instead. getAddon returns a content process from a pool of N processes, rather than just a singleton. Furthermore, this pool is separate from the singleton used for <brower> elements with type="content".

This bug is currently blocked on bug 674217, as I need L1 commit rights before I am able to push to the temporary branch we've created for this prototype.
Depends on: 674217
Priority: -- → P1
Target Milestone: --- → 1.3
Assignee: nobody → ejpbruel
(Pushing all open bugs to the --- milestone for the new triage system)
Target Milestone: 1.3 → ---
(Assignee)

Comment 3

7 years ago
The prototype has since been pushed to the temporary branch and is now being tested, so this bug can be closed as resolved.
Status: NEW → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.