@Martin There is a pref (dom.ipc.processCount.webLargeAllocation - default 2) which controls the maximum number of processes which may be allocated to Large-Allocation processes. Any requests past that number (firefox-globally) will not cause new processes to be created.
@Chris the Large-Allocation header acts as a hint. Currently I intend to use dedicated processes on 64-bit as well as 32-bit, as there are some minor differences in behavior due to there being multiple content processes when loaded in the Large-Allocation process. In order to ensure that people who are developing games don't run into these issues, I want to make them (who will have 64-bit machines most likely) run into these issues before reaching production. In the future, when we are shipping e10s-multi, we can consider ignoring the large allocation hint on 64-bit architectures, as there will be a much much lower chance of multiple content process only differences affecting the program. On Wed, Jan 18, 2017 at 4:03 PM, Martin Thomson <m...@mozilla.com> wrote: > On Thu, Jan 19, 2017 at 9:21 AM, Michael Layzell > <mich...@thelayzells.com> wrote: > > Security & Privacy Concerns: none > > I doubt that this is true. You have provided a way for sites to gain > a whole process to themselves, on request. Denial of service seems > like something that would need to be considered if you intend to ship > this. > _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
