Julien Wajsberg <[email protected]> writes: > Le 16/04/2014 20:24, Kyle Huey a écrit : >> >> The correct way to think of it is that revoking a blob URL only >> affects the network level. If loading/etc is complete it will >> generally have no effect. There are certain caveats to this for >> things that happen lazily (such as CSS background image loading, which >> only happens when there is an element that actually has the image as a >> background). >> > So, does that mean that when we use a blob url, imglib keeps a second > copy of the compressed image data, and we end up with 2 copies of that > data until we revoke the blob url? Or somehow is this data mmap-ed or > something, so that it's shared in a way that it's not freed when we > revoke the blob url?
imglib doesn't know from where the image is loaded so it copies everything it received. So yes, you could get 2 copies of that data if it's a memory-backed Blob. _______________________________________________ dev-b2g mailing list [email protected] https://lists.mozilla.org/listinfo/dev-b2g
