- From: Bronislav Klučka <Bronislav.Klucka@bauglir.com>
- Date: Mon, 30 Jan 2012 17:15:59 +0100
- To: public-webapps@w3.org
On 30.1.2012 16:56, Boris Zbarsky wrote:
> On 1/30/12 10:40 AM, Bronislav Klučka wrote:
>> img1 = document.getElementById("my-image");
>> img1.src = URL.createObjectUrl(myBlob);
>> img2.src = img1.src;
>> should work like a charm and the URL and blob will be released as soon
>> as all references will be 0 (destroying the image)
>
> No, it won't. As currently specced it will be released when the
> document goes away or when the url created via createObjectURL is
> manually revoked. That's precisely the problem.
>
> -Boris
>
In this case you got me... what sense does it make? If there is no
reference to original blob or any other object using that URL, why is it
kept?
so just a line
URL.createObjectUrl(blob)
creates a memory leak? Heh?
Which brink me to my previous question, what happened to Blob.URL? Just
brink it back and this whole conversation can go away...
Brona
Received on Monday, 30 January 2012 16:16:38 UTC