Bug 551169 was exposed by a very large Function.apply call (ie huge array). In conjunction with AIR where USE_SYSTEM_MALLOC is defined this results in a large GCRoot being created with system malloc. Upon free this memory is returned to the system due to the malloc policy of going straight to the OS for alloc requests over a certain size (128k I believe). Anyways we need a (deep?) test case that makes a huge (multi megabyte) Array and passes it to Function.apply and we it to run in normal builds and a USE_SYSTEM_MALLOC build.
Priority: -- → P3
Target Milestone: --- → flash10.1.1
Created attachment 435904 [details] Sketch for a test case This needs to be massaged to fit into our testing framework probably, and presumably it could run many iterations to trigger GC etc, but I think it's more or less what's called for.
Created attachment 437079 [details] [diff] [review] Test case This becomes test/acceptance/ecma3/Function/apply_001.as.
Attachment #437079 - Flags: review?(treilly) → review+
tamarin-redux-argo changeset: 3937:240556a76b45
Status: NEW → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.