Re: [w3c/FileAPI] Remove definition of Blob.close() and all related terms. (#68)

@annevk 


At some point Chromium _did_ implement `close` https://github.com/guest271314/MediaFragmentRecorder/blob/master/demos/recordMediaFragments.html#L221. 

> You can just let it GC. 

That is an extremely broad statement without clear parameters, including the specific processing steps of "just let it" before even reaching "GC".

What is the available RAM and HD space at the device where you are able to create 1000 `Blob` objects without the tab crashing? 

Running this https://github.com/guest271314/MediaFragmentRecorder/blob/master/demos/recordMediaFragments.html, where multiple `Blob` and `Blob URL`s are created, multiple times at a device having minimal RAM or available HD space has arbitrarily and inconsistently crashed the browser tab at Chromium. 


When the `Blob` or `Blob URL` was closed or revoked the same was reflected at `chrome://blob-internals`.

What is the canonical approach to remove/purge the `Blob` snapshot state from the file which stores that data at Chromium and Firefox?




-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/FileAPI/pull/68#issuecomment-366776560