Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Managed memory leak in ClrFunc::Initialize #128

Closed
tjanczuk opened this issue Apr 25, 2014 · 0 comments
Closed

Managed memory leak in ClrFunc::Initialize #128

tjanczuk opened this issue Apr 25, 2014 · 0 comments
Labels

Comments

@tjanczuk
Copy link
Owner

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant