News for hackers. Stuff that matters.

A comment on Memory Usage of Firefox with e10s Enabled. Parent comment

Re:Memory Usage of Firefox with e10s Enabled by lucian1900 on Friday February 12, 2016 @02:31PM (#11089816)
Actually, Chrome does process-per-domain. Almost always several tabs of the same domain will share a process. You can check this by killing one process and seeing lots of tabs go away.
[ Parent | on HN ]
Re:Memory Usage of Firefox with e10s Enabled by justinschuh on Friday February 12, 2016 @03:46PM (#11090414)
No. We currently mostly do process-per-tab, but it gets complicated depending on how exactly a given window/tab was opened and certain resource heuristics. We're moving to process-per-origin[1], largely for the security improvement. But, that's been a huge, multi-year engineering effort that's only now approaching fruition.

[1] https://www.chromium.org/developers/design-documents/site-is...

[ Parent | on HN ]
Re:Memory Usage of Firefox with e10s Enabled by lucian1900 on Saturday February 13, 2016 @12:17AM (#11092665)
I see.

So the reason more than one tab will crash when killing a process is that all those processes were sharing a resource of some sort?

[ Parent | on HN ]