On Mon, Jun 18, 2018 at 09:19:18PM +0100, Gijs Kruitbosch wrote:
Hey,
This sounds really interesting. However, wouldn't this mean that we
will do a process switch for the tab's browser whenever we load a URL
in the same tab that has AS in it? Or would you still intend to run
the actual AS new tab page in a "normal" tab process?
If it *would* mean a process switch, we may want to take another look
at some of the bugs relating to those (process switches are currently
relatively rare) and re-prioritize them.
It will definitely need to mean a process switch. For the sake
of Fission, we really need to never run content JS in the same
process that AS runs in. And for the sake of content process
memshrink, we really need to not load AS into multiple content
processes.
On 18/06/2018 20:35, Mike Conley wrote:
(posted on both dev-platform and firefox-dev. Please send replies to
dev-platform)
Hello all,
Just sending a quick note to let you know that I've filed bug 1469072[1] to
move Activity Stream into its own content process.
This is something that Fission needs, but we're hoping to squeeze some
performance benefits out of it as well by reducing, reusing and recycling
various Activity Stream things since they'll all be contained within a
single process. It might also allow us to cache more Activity Stream
scripts in ScriptPreloader[2], since we can reasonably assume only trusted
JavaScript will be running within the Activity Stream content process.
This work is going to be handled by my intern, Jay Lim. If you have any
concerns with this plan, please bring them to my attention - commenting in
the bug, emailing me, or responding to this thread on dev-platform is fine.
Thanks!
-Mike
[1]: https://bugzilla.mozilla.org/show_bug.cgi?id=1469072
[2]: I wrote about ScriptPreloader on my blog here:
https://mikeconley.ca/blog/2018/05/30/firefox-performance-update-9/
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
