We're using Runtime.callFunctionOn at a very high rate, and the compiled functions seem to be leaking -- even when using node.js' `global.gc()` or `HeapProfiler.collectGarbage` to manually trigger a full GC before taking a heapdump. Looking at a heapdump, there are many more "(compiled code)" objects which contain the functions passed to callFunctionOn.
I'm reviewing the code for callFunctionOn and the use of a v8::Local seems to suggest that the function should be freed immediately after that C++ scope exits, so I'm confused. (code can be found here - https://source.chromium.org/chromium/chromium/src/+/master:v8/src/inspector/v8-runtime-agent-impl.cc;l=111;drc=d0e87c5b5ac8f1d884f5899f4b63967fea784d07;bpv=0;bpt=1 ) Am I wrong? When would the functions be garbage collected in that case? -- -- v8-dev mailing list [email protected] http://groups.google.com/group/v8-dev --- You received this message because you are subscribed to the Google Groups "v8-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/v8-dev/1902c9ed-d4ba-4d0a-a618-89e8ca678c09n%40googlegroups.com.
