-
Notifications
You must be signed in to change notification settings - Fork 30.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
[v8.x] n-api: finalize during second-pass callback #26060
Closed
gabrielschulhof
wants to merge
1
commit into
nodejs:v8.x-staging
from
gabrielschulhof:25927-finalize-during-second-pass-callback-v8.x
Closed
[v8.x] n-api: finalize during second-pass callback #26060
gabrielschulhof
wants to merge
1
commit into
nodejs:v8.x-staging
from
gabrielschulhof:25927-finalize-during-second-pass-callback-v8.x
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
nodejs-github-bot
added
c++
Issues and PRs that require attention from people who are familiar with C++.
node-api
Issues and PRs related to the Node-API.
v8.x
labels
Feb 12, 2019
gabrielschulhof
force-pushed
the
25927-finalize-during-second-pass-callback-v8.x
branch
from
February 12, 2019 22:11
ad93fae
to
9a4f8dc
Compare
mhdawson
approved these changes
Feb 20, 2019
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.
LGTM
Calling into the engine from a weak callback is unsafe, however, the engine offers a way to attach a second-pass weak callback which gets called when it is safe to call into JavaScript. This moves the point at which the N-API finalize callback gets called to this latter point. Fixes: nodejs#25927 PR-URL: nodejs#25992 Backport-PR-URL: nodejs#26060 Reviewed-By: Anna Henningsen <anna@addaleax.net> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Michael Dawson <michael_dawson@ca.ibm.com>
gabrielschulhof
force-pushed
the
25927-finalize-during-second-pass-callback-v8.x
branch
from
March 4, 2019 18:34
9a4f8dc
to
c1a1ea1
Compare
BethGriggs
approved these changes
Mar 20, 2019
Landed on v8.x-staging. |
BethGriggs
pushed a commit
that referenced
this pull request
Mar 20, 2019
Calling into the engine from a weak callback is unsafe, however, the engine offers a way to attach a second-pass weak callback which gets called when it is safe to call into JavaScript. This moves the point at which the N-API finalize callback gets called to this latter point. Fixes: #25927 PR-URL: #25992 Backport-PR-URL: #26060 Reviewed-By: Anna Henningsen <anna@addaleax.net> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Michael Dawson <michael_dawson@ca.ibm.com>
gabrielschulhof
deleted the
25927-finalize-during-second-pass-callback-v8.x
branch
June 14, 2019 23:51
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Calling into the engine from a weak callback is unsafe, however, the
engine offers a way to attach a second-pass weak callback which gets
called when it is safe to call into JavaScript. This moves the point
at which the N-API finalize callback gets called to this latter point.
Fixes: #25927
PR-URL: #25992
Backport-PR-URL: #26058
Checklist
make -j4 test
(UNIX), orvcbuild test
(Windows) passes