Mike Conley (:mconley) (:⚙️) Reporter
	Description • 8 years ago

We use BlobURLs when the user right-clicks on a <canvas> and does things like viewing the canvas on its own, or saving it to disk.

The problem is that BlobURLs keep the resources around that they refer to because we can no longer GC things that _might_ still be referred to by URL.

This means that we'll leak the resources until we call URL.revokeObjectURL.

	Eric Rahm [:erahm]
	Comment 1 • 8 years ago

Mike, is it possible to provide a sample web page to reproduce this? Also are you saying we leak the blobs completely, or just don't free them in a timely fashion?

	Mike Conley (:mconley) (:⚙️) Reporter
	Comment 2 • 8 years ago

Sure, I think so.

1) Visit http://www.blobsallad.se/
2) Right click on the animated blob, and choose "View Image"

Notice that the Blob URL that is produced is blob:null/8e59ee06-23a9-3641-9e6e-520eb16ca72f. That "null" means that it's not bound to a particular origin, meaning (I believe) that it won't be cleared out when all documents at that origin are gone.

And I think that means that we're holding onto the resource indefinitely, since we never revoke the Blob URL.