4 ms·

hi, co-author of the blog post here. There is a more detailed blog post explaining how Site Isolation is better than the Electrolysis architecture here - https:

by annyg 5y ago

hi, co-author of the blog post here. There is a more detailed blog post explaining how Site Isolation is better than the Electrolysis architecture here - https://hacks.mozilla.org/2021/05/introducing-firefox-new-site-isolation-security-architecture/ https://hacks.mozilla.org/2021/05/introducing-firefox-new-si... (also linked to from the security blog post). Hope this is helpful!

jzelinskie 5y ago
Thanks for this link. Not sure how I missed it when it's the very last word, haha. I'm not sure what gave me the impression but, in my mind "process-per-tab" and "Electrolysis" were linked, but that was a misconception: >In great detail, (as of April 2021) Firefox’s parent process launches a fixed number of processes: eight web content processes, up to two additional semi-privileged web content processes, and four utility processes for web extensions, GPU operations, networking, and media decoding. >While separating content into currently eight web content processes already provides a solid foundation, it does not meet the security standards of Mozilla because it allows two completely different sites to end up in the same operating system process and, therefore, share process memory. To counter this, we are targeting a Site Isolation architecture that loads every single site into its own process.
- cpeterso 5y ago
  > I'm not sure what gave me the impression but, in my mind "process-per-tab" and "Electrolysis" were linked, but that was a misconception: Your impression was mostly correct. Electrolysis is basically process-per-tab until you reach eight tabs, but after that, tabs start sharing those eight content processes.
  - cpeterso 5y ago
    Correction to my earlier statement: the initial version of Electrolysis had just one content process (that could be sandboxed apart from the browser parent process), but was soon followed up with "e10s-multi" with multiple content processes.
- pseudalopex 5y ago
  > I'm not sure what gave me the impression but, in my mind "process-per-tab" and "Electrolysis" were linked This always was a long term goal I think. It's per site not per tab though.
gostsamo 5y ago
Hi, I'm a blind user and I'm just dropping to say a big thank you for the excellent alt text to the diagrams in the hacks post. Thanks for the browser work as well!
- arkitaip 5y ago
  Thank YOU for writing comments like these - it encourages us web devs to work harder on accessibility.
- deleted 5y ago
  [deleted]
yorwba 5y ago
I enjoyed the illustrations, but you should try looking at your article in Firefox for Android: all pictures overflow to the right and it's not even possible to scroll horizontally to see the rest.

by annyg 5y ago

jzelinskie 5y ago

Thanks for this link. Not sure how I missed it when it's the very last word, haha. I'm not sure what gave me the impression but, in my mind "process-per-tab" and "Electrolysis" were linked, but that was a misconception: >In great detail, (as of April 2021) Firefox’s parent process launches a fixed number of processes: eight web content processes, up to two additional semi-privileged web content processes, and four utility processes for web extensions, GPU operations, networking, and media decoding. >While separating content into currently eight web content processes already provides a solid foundation, it does not meet the security standards of Mozilla because it allows two completely different sites to end up in the same operating system process and, therefore, share process memory. To counter this, we are targeting a Site Isolation architecture that loads every single site into its own process.

cpeterso 5y ago
> I'm not sure what gave me the impression but, in my mind "process-per-tab" and "Electrolysis" were linked, but that was a misconception: Your impression was mostly correct. Electrolysis is basically process-per-tab until you reach eight tabs, but after that, tabs start sharing those eight content processes.
- cpeterso 5y ago
  Correction to my earlier statement: the initial version of Electrolysis had just one content process (that could be sandboxed apart from the browser parent process), but was soon followed up with "e10s-multi" with multiple content processes.
pseudalopex 5y ago
> I'm not sure what gave me the impression but, in my mind "process-per-tab" and "Electrolysis" were linked This always was a long term goal I think. It's per site not per tab though.

gostsamo 5y ago

Hi, I'm a blind user and I'm just dropping to say a big thank you for the excellent alt text to the diagrams in the hacks post. Thanks for the browser work as well!

arkitaip 5y ago
Thank YOU for writing comments like these - it encourages us web devs to work harder on accessibility.
deleted 5y ago
[deleted]

yorwba 5y ago

I enjoyed the illustrations, but you should try looking at your article in Firefox for Android: all pictures overflow to the right and it's not even possible to scroll horizontally to see the rest.