-
-
Notifications
You must be signed in to change notification settings - Fork 21.1k
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
Fix JavaScript callback memory leak issue #81105
Fix JavaScript callback memory leak issue #81105
Conversation
For the record, your commit seems not to be linked to your GitHub account. See: Why are my commits linked to the wrong user? for more info. |
Yes I didn't set Git credentials or set wrongly. I'll have a look and have a check on it again |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looking great 🏆
Thank you for debugging and fixing this 🥳 !
Just a small nit pick.... the argsProxy.unref();
could go right after the func(
call.
Could you please squash your commits into one? Make sure that the final commit has a short but descriptive message (the title of this PR is a good option). See this documentation, if you need help with squashing. |
d7053bc
to
f528ffb
Compare
You have reset the authors of several commits when rebasing |
f528ffb
to
5aec6c9
Compare
5aec6c9
to
6a90164
Compare
I tried to rebase it correctly but seemed like Faless's credit is missing :( |
I think it's fine, a small nitpick doesn't necessarily require co-crediting. |
Thanks! |
Cherry-picked for 4.1.3. |
Follows #81090 for
master
branch. I noticed that inmaster
it supports returning value so I put theunref
the last until value return occurs.