Bug 187764 - Memory leak when using requestAnimationFrame
Summary: Memory leak when using requestAnimationFrame
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: JavaScriptCore (show other bugs)
Version: Safari Technology Preview
Hardware: PC Windows 10
: P2 Blocker
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-07-18 09:45 PDT by Plamen
Modified: 2018-07-26 08:25 PDT (History)
1 user (show)

See Also:


Attachments
a minimal example of a leaking issue (580 bytes, text/html)
2018-07-18 09:45 PDT, Plamen
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Plamen 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.
Comment 1 Simon Fraser (smfr) 2018-07-20 21:22:48 PDT
Safari Tech Preview is now at version 61. Does this still reproduce?
Comment 2 Plamen 2018-07-26 00:11:10 PDT
unfortunately, it is no  trivial for me to switch to STP 61
Comment 3 Simon Fraser (smfr) 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?