>Welcome to the first edition of the Fission MemShrink newsletter.[1]

This is awesome and critical.

I'll note (and many of you know this well) that in addition to getting
rid of allocations (or making them lazy), another primary solution is to
move data out of the Content processes, and into the master process (or
some other shared process, if that's advisable for security or other
reasons), and access the data over IPC.  Or you can move it to a shared
memory block (with appropriate locking if not static).  For example, on
linux one of our worst offenders is fontconfig; Chrome for example
remotes much of that to the master process.

Randell Jesup, Mozilla Corp
remove "news" for personal email
dev-platform mailing list

Reply via email to