Re: Images in a Multiprocess World

On 6/23/09 12:08 PM, Joe Drew wrote:
> 
> On Jun 23, 2009, at 10:17 AM, Benjamin Smedberg wrote:
> 
>> I would hope, though, that the network cache, which is planned to be
>> shared,
>> would take care of making sure we don't download images twice. Is image
>> decoding really an expensive-enough operation that we want to add lots of
>> extra machinery?
> 
> We already have that extra machinery in the form of the image cache.
> Decoding on its own isn't that expensive, but doing it over and over for
> the same images sucks, and breaks some web consumers (see bug 466586).

I believe that with multi-process we're unlikely to be using the same image
in multiple tabs, and we could just use a per-process image cache. Are you
saying there are web-compat issues where if we had a per-process image cache
backed by the necko HTTP cache we'd somehow cause problems for websites?

--BDS