-
Notifications
You must be signed in to change notification settings - Fork 30k
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
src: restrict unloading addons to Worker threads #25577
Conversation
CI: https://ci.nodejs.org/job/node-test-pull-request/20205/ (:heavy_check_mark:) Please 👍 this comment to approve fast-tracking – it fixes a regression in 11.7.0. |
This needs a second review. (/cc @nodejs/workers maybe?) |
Code LGTM, but I don't feel knowledgeable enough in this area.
Unloading native addons from the main thread was an (presumably unintended) significant breaking change, because addons may rely on their memory being available after an `Environment` exits. This patch only restricts this to Worker threads, at least for the time being, and thus matches the behaviour from nodejs#23319. Refs: nodejs#24861 Refs: nodejs#23319
a6186f8
to
d7d409a
Compare
@bnoordhuis Thanks, done! |
Windows failure looks weird. Rebuild: https://ci.nodejs.org/job/node-test-commit-windows-fanned/24153/ (✔️ ) |
Landed in ef1c639. |
Unloading native addons from the main thread was an (presumably unintended) significant breaking change, because addons may rely on their memory being available after an `Environment` exits. This patch only restricts this to Worker threads, at least for the time being, and thus matches the behaviour from #23319. PR-URL: #25577 Refs: #24861 Refs: #23319 Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Daniel Bevenius <[email protected]> Reviewed-By: Ben Noordhuis <[email protected]>
Unloading native addons from the main thread was an (presumably unintended) significant breaking change, because addons may rely on their memory being available after an `Environment` exits. This patch only restricts this to Worker threads, at least for the time being, and thus matches the behaviour from #23319. PR-URL: #25577 Refs: #24861 Refs: #23319 Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Daniel Bevenius <[email protected]> Reviewed-By: Ben Noordhuis <[email protected]>
Unloading native addons from the main thread was an (presumably
unintended) significant breaking change, because addons may
rely on their memory being available after an
Environment
exits.This patch only restricts this to Worker threads, at least for the
time being, and thus matches the behaviour from #23319.
Refs: #24861
Refs: #23319
Checklist
make -j4 test
(UNIX), orvcbuild test
(Windows) passes