You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Both Windows and Mono versions of ClrFunc::Initialize will leak managed V8 memory due to allocations of v8::Function that are not garbage collected until the process terminates. Underlying reasons and fix is same as in #125.
The workaround for JavaScript proxies to CLR functions is to allocate them once. This covers majority of scenarios. This does not cover CLR code returning other CLR functions as part of the result of the call, as in https://github.com/tjanczuk/edge/blob/master/samples/110_clr_instance.js
The text was updated successfully, but these errors were encountered:
Both Windows and Mono versions of ClrFunc::Initialize will leak managed V8 memory due to allocations of v8::Function that are not garbage collected until the process terminates. Underlying reasons and fix is same as in #125.
The workaround for JavaScript proxies to CLR functions is to allocate them once. This covers majority of scenarios. This does not cover CLR code returning other CLR functions as part of the result of the call, as in https://github.com/tjanczuk/edge/blob/master/samples/110_clr_instance.js
The text was updated successfully, but these errors were encountered: