[Bug 16790] The term microtask should be defined

https://www.w3.org/Bugs/Public/show_bug.cgi?id=16790

--- Comment #8 from Glenn Maynard <glenn@zewt.org> 2012-04-18 21:44:42 UTC ---
(In reply to comment #7)
> If the author knows that the URL isn't being used anymore, I've nothing against
> the author revoking it. But the browser doesn't know, so the browser shouldn't
> do it automatically.

The browser does know, because the user has requested it explicitly:

var url = URL.createObjectUrl(myBlob, {autoRevoke: true});
img.src = url;

This avoids the glaring problem with object URLs, by making it impossible to
accidentally leak myBlob.  (It also avoids the problems with previous "revoke
on first use" proposals, by eliminating any possible dependencies on task order
across task queues.)

> Paging the data to disk is sufficient, and cheap.

You're arguing that never freeing memory, and letting everything page to disk
forever, is an acceptable memory management design?  That's crazy.  If I have
an image viewer that receives high-resolution PNGs as blobs (for example, for
examining or editing print-resolution images), and then hands them off to
HTMLImageElement.src as object URLs to be viewed (or loaded into WebGL), that
will quickly explode into gigabytes of data that has to be written to disk and
then kept around for the lifetime of the page.

Also, my phone doesn't have a disk drive, and internal storage is very limited.

> Are we going to be specifying all the different places that can happen? I guess
> if we specify it in detail that wouldn't be so bad.

Hopefully it can be done in a way that minimizes the amount of work high-level
specs like img.src and XHR need to do.

-- 
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Received on Wednesday, 18 April 2012 21:44:49 UTC