This is true, but I'm not sure how this is worse than other mechanisms which can currently be used to deny other pages resources, such as allocating and leaking large amounts of memory or pegging the event loop.
On Wed, Jan 18, 2017 at 4:38 PM, Martin Thomson <m...@mozilla.com> wrote: > On Thu, Jan 19, 2017 at 10:17 AM, Michael Layzell > <mich...@thelayzells.com> wrote: > > @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. > > That prevents unlimited spawning of processes, but doesn't stop a site > from blocking another one from getting a new process. > _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
