114824 – Garbage Collection of Typed Arrays Fails

RESOLVED DUPLICATE of bug 119064 114824

Garbage Collection of Typed Arrays Fails

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

Summary Garbage Collection of Typed Arrays Fails

Amit Kapadia

Reported 2013-04-18 13:05:49 PDT

Created attachment 198755 [details] Example of typed array initialization and failure of garbage collector. Steps to reproduce the problem: 1. Define a function that initializes a typed array. 2. Execute the function. 3. Observe the typed array not being garbage collected when falling out of scope. The garbage collector should release memory from all variables defined in the function closure. Memory associated with the typed array is not released at any point during the life cycle of the web app. Memory is not released on tab close, but only on application close. Additionally, allocating a typed array seems to consume more memory than it should. For example, var arr = new Float32Array(268435456); allocates 1 gigabyte for array storage; however, WebKit consumes ~4 GB.

Attachments
Example of typed array initialization and failure of garbage collector. (638 bytes, text/html) 2013-04-18 13:05 PDT, Amit Kapadia	no flags	Details
View All Add attachment proposed patch, testcase, etc.

Oliver Hunt

Comment 1 2013-04-20 11:32:57 PDT

Check on a webkit nightly, my testing shows this as fixed

Amit Kapadia

Comment 2 2013-04-22 08:20:51 PDT

Oliver, what type of tests did you conduct? This is still an open issue on my end (using WebKit nightly). If you open the Activity Monitor, you will see 500 MB allocated by "SafariForWebKitDevelopment Web Content". This memory is not released until the application closes.

Amit Kapadia

Comment 3 2013-04-30 07:50:47 PDT

This bug also exists when initializing instances of ArrayBuffer. Webkit nightly does not release memory until the application closes.

Alexey Proskuryakov

Comment 4 2013-07-24 11:12:48 PDT