Bug 187764

Summary: Memory leak when using requestAnimationFrame
Product: WebKit Reporter: Plamen <plamend>
Component: JavaScriptCoreAssignee: Nobody <webkit-unassigned>
Status: NEW    
Severity: Blocker CC: simon.fraser
Priority: P2    
Version: Safari Technology Preview   
Hardware: PC   
OS: Windows 10   
Attachments:
Description Flags
a minimal example of a leaking issue none

Plamen
Reported 2018-07-18 09:45:56 PDT
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.
Attachments
a minimal example of a leaking issue (580 bytes, text/html)
2018-07-18 09:45 PDT, Plamen 		no flags
Details
View All Add attachment proposed patch, testcase, etc.
Simon Fraser (smfr)
Comment 1 2018-07-20 21:22:48 PDT
Safari Tech Preview is now at version 61. Does this still reproduce?
Plamen
Comment 2 2018-07-26 00:11:10 PDT
unfortunately, it is no trivial for me to switch to STP 61
Simon Fraser (smfr)
Comment 3 2018-07-26 08:25:21 PDT
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?
Note You need to log in before you can comment on or make changes to this bug.