[Webkit-unassigned] [Bug 257371] Revoking with URL.revokeObjectURL() does not adequately free memory

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=257371

--- Comment #5 from Nathan <nathan at shareup.app> ---
@youenn the jsfiddle you shared appears to only have 37 unsplash URLs in the array, so it's not actually creating 100 object URLs during each run. This made the test much easier for the browser to run, and I think doesn't demonstrate the issue as readily unless you run it with a much higher number of pages/batches.

I've created a jsfiddle here which has all unsplash images from my original demo and I've verified that it is actually creating 100 object URLs now during each run. Here is the URL to the forked jsfiddle I made: https://jsfiddle.net/myobie/x8z7kh9a/8/

(It's tough for jsfiddle to render the JS code with that many URLs... sorry.)

I ran it on macOS 13.4, iPhone 14 with iOS 16.5, and an iPhone 14 Pro with iOS 16.5.

macOS: made it through the test. The test appears to run smoother than it did before, but maybe that is just my perception. I don't have actual data to back that up.

iPhone 14: crashed the tab before it made it through the test.

iPhone 14 Pro: took a while, but it did make it through the entire test. 

You mentioned that there was some work done in trunk recently released to this. Are there any tests to verify that the memory is cleaned up when the URL is revoked?

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20230613/2111e4ec/attachment.htm>