Hey,

Basically, I'd like to know whether it's better to revoke a blob URL
just after an image has been loaded, even if it's still displayed, or to
keep the blob url valid until the image is hidden.

Here is a rationale I can't remove from my mind:
* the image as a blob will likely be smaller (because it's compressed)
than the image as displayed (because it's uncompressed)
* what should gecko do once the image is displayed? We will eventually
need the uncompressed data to repaint.
* if the source is a http URL or a data URL, then gecko is confident
that the source will always be available; therefore it could discard any
uncompressed data in case of memory pressure, because it could calculate
it again from the source.
* if the source is a blob URL and is revoked, then gecko won't be able
to get the uncompressed data once it's discarded, therefore we need to
keep it in memory.
* if the source is a blob URL and still valid, we can argue both behaviors.

I don't know _at all_ how much of what I describe here is true/wrong,
and therefore I hope somebody will be able to answer this, not in terms
of "what I think happens" but in terms of "what gecko is doing".

Thanks a lot in advance!
-- 
Julien

Attachment: signature.asc
Description: OpenPGP digital signature

_______________________________________________
dev-b2g mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-b2g

Reply via email to