Confirmed users
1,094
edits
Firefox/AddOns/Status/current: Difference between revisions
Jump to navigation
Jump to search
Firefox/AddOns/Status/current (view source)
Revision as of 18:25, 14 February 2017
, 14 February 2017→Schedule: update
Sescalante (talk | contribs) |
Sescalante (talk | contribs) (→Schedule: update) |
||
| Line 200: | Line 200: | ||
== Schedule == | == Schedule == | ||
=== Multiplecontent Processes === | |||
A [https://wiki.mozilla.org/Electrolysis/Multiple_content_processes multiple content processes] model (e10s-multi) is starting to roll out in Nightly 54/55. It required e10s, or multi content processes will not be applied. It is not expected to go to release until mid-2017 and for the most part should not impact add-ons. | |||
<p></p> | |||
Possible [https://wiki.mozilla.org/Electrolysis/Multiple_content_processes#Add-ons add-ons] that could be impacted: | |||
*With multi-content processes, JSM has to be loaded for every process. If JSM is loaded only once and expected to run globally, the add-on may break. Process script is the suggested way for observer registration instead of JSMs. | |||
*SDK based add-ons can come with a big memory overhead per process. If the SDK loader (especially [https://bugzilla.mozilla.org/show_bug.cgi?id=1308860#c0 node.js]) is slow, it will be slow multiple times now in each process. | |||
*If the add-on assumes that they only have one content process, it could falsely expect that observer and category registration to run only once. Instead it will run once per content process. If the add-on then uses it for something else (ex: to try sending some important message to the parent side that the content side is active) the parent may get multiple messages and some of the messages may arrive before other content processes are ready. | |||
<p></p> | |||
There is a preference you can check to see if multiple content processes are enabled. In about:config, a dom.ipc.processCount of 1 means that multiple content processes are not enabled. Any number higher than 1 and the browser is using multiple processes. To troubleshoot if your add-on is experiencing issues from multiple content processes, you can reset the number to 1 to see if the issue goes away. | |||