Fission Engineering Newsletter #1

Kris Maglione kmaglione at
Thu Feb 14 05:19:22 UTC 2019

On Wed, Feb 13, 2019 at 09:06:57PM -0800, Matthew N. wrote:
>On 2019-02-13 9:02 p.m., Tom Ritter wrote:
>>On Wed, Feb 13, 2019 at 9:48 PM Matthew N. <MattN at> wrote:
>>>What about doing better sandboxing of the content
>>>process (e.g. ensuring a compromised process can't request information
>>>from the parent that isn't relevant to it)?
>>This is
>>Its major sub-bug that pertains specifically to IPC is
>>For now, the focus on Fission is just getting it working, these
>>efforts (stronger sandboxing) will come after that.
>I quoted the part about the milestone flag as I was wondering whether 
>we are supposed to nominate such bugs now or we should only be 
>nominating functional bugs? (Same goes for memory usage ones.)

Content process memory usage is a blocker for shipping Fission 
(though it doesn't block milestone 1). Stronger sandboxing is 
important post-Fission, but it doesn't block shipping.

More information about the firefox-dev mailing list