Re: Images in a Multiprocess World

Bobby Holley wrote:
> I put together a design document on the work I'm going to be doing on 
> multiprocess image handling for Electrolysis. It's on the wiki at 
> https://wiki.mozilla.org/Multiprocess_Images
> 
> I'd appreciate any input or feedback on the matter.

Some thoughts:

1)  What are the benefits of sharing the image cache between all content 
processes?  Some of the drawbacks are obvious: stopping animations in 
one tab stops animations of the same images in other tabs, for example. 
  How common is it that different tabs/windows really share the same 
images?  Would things be better in that regard if we used 
process-per-domain or some such?  Or otherwise grouped multiple tabs 
into a single process?

2)  The current plan assumes that content/layout consumers will just 
keep calling loadImage.  But they need to make a content policy call 
before doing that; will content policies run in the renderer processes 
or in chrome?  If the latter, then presumably the loadImage shouldn't 
run in the renderer process either.

3) Similar for security checks (which also need to happen before loadImage).

-Boris