| Summary: | Memory leak when using requestAnimationFrame | ||||||
|---|---|---|---|---|---|---|---|
| Product: | WebKit | Reporter: | Plamen <plamend> | ||||
| Component: | JavaScriptCore | Assignee: | Nobody <webkit-unassigned> | ||||
| Status: | NEW --- | ||||||
| Severity: | Blocker | CC: | simon.fraser | ||||
| Priority: | P2 | ||||||
| Version: | Safari Technology Preview | ||||||
| Hardware: | PC | ||||||
| OS: | Windows 10 | ||||||
| Attachments: |
|
||||||
Safari Tech Preview is now at version 61. Does this still reproduce? unfortunately, it is no trivial for me to switch to STP 61 Using the web inspector's heap snapshot with your test case, I can't see any memory growth with your test case in STP 61. How are you measuring heap growth? |
Created attachment 345254 [details] a minimal example of a leaking issue It seems that if I have a lambda function which only assigned a value to a global variable and pass those lambda function to requestAnimationFrame the heap size growing all the time. The growing of the heap depends on the size of the value that I want to assign. I am using "safari-technology-preview-34" also If I pass an empty lambda function to "requestAnimationFrame" the "WeakSet::addAllocator" add a new block every time.