-
-
Notifications
You must be signed in to change notification settings - Fork 31.6k
[13.2.0] Assertion `(new_handler_count) >= (0)' failed #30581
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Comments
Here’s a quick fix if anybody wants to open a PR and get 13.2.1 out: diff --git a/src/signal_wrap.cc b/src/signal_wrap.cc
index cf67dc590f6d..bc2d9f1e355e 100644
--- a/src/signal_wrap.cc
+++ b/src/signal_wrap.cc
@@ -91,7 +91,10 @@ class SignalWrap : public HandleWrap {
}
void Close(v8::Local<v8::Value> close_callback) override {
- if (active_) DecreaseSignalHandlerCount(handle_.signum);
+ if (active_) {
+ DecreaseSignalHandlerCount(handle_.signum);
+ active_ = false;
+ }
HandleWrap::Close(close_callback);
}
I’ll try to look more into why this is happening tomorrow, it’s an odd bug and points to us attempting to close a signal handle multiple times. |
seems like #30582 fixes it |
Closed by #30582. |
Thanks! ❤️ |
When can we see this in a patch release? |
That depends on @nodejs/releasers – I figure we’d want to get #30586 resolved soon too, so maybe after that? |
Fwiw, it should work well enough as a temporary workaround to use something like
|
Refs: #30581 Refs: #30582 PR-URL: #30589 Refs: #30581 Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Gireesh Punathil <gpunathi@in.ibm.com> Reviewed-By: Richard Lau <riclau@uk.ibm.com> Reviewed-By: Beth Griggs <Bethany.Griggs@uk.ibm.com> Reviewed-By: Michael Dawson <michael_dawson@ca.ibm.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Refs: #30581 Refs: #30582 PR-URL: #30589 Refs: #30581 Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Gireesh Punathil <gpunathi@in.ibm.com> Reviewed-By: Richard Lau <riclau@uk.ibm.com> Reviewed-By: Beth Griggs <Bethany.Griggs@uk.ibm.com> Reviewed-By: Michael Dawson <michael_dawson@ca.ibm.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Refs: #30581 Refs: #30582 PR-URL: #30589 Refs: #30581 Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Gireesh Punathil <gpunathi@in.ibm.com> Reviewed-By: Richard Lau <riclau@uk.ibm.com> Reviewed-By: Beth Griggs <Bethany.Griggs@uk.ibm.com> Reviewed-By: Michael Dawson <michael_dawson@ca.ibm.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
@nodejs/releasers Can somebody do a v13.x this week? |
@BridgeAR signed up for one this week: nodejs/Release#487 |
Refs: #30581 Refs: #30582 PR-URL: #30589 Refs: #30581 Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Gireesh Punathil <gpunathi@in.ibm.com> Reviewed-By: Richard Lau <riclau@uk.ibm.com> Reviewed-By: Beth Griggs <Bethany.Griggs@uk.ibm.com> Reviewed-By: Michael Dawson <michael_dawson@ca.ibm.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
v13.2.0
Linux nicolo-XPS-15-9570 5.3.0-23-generic #25-Ubuntu SMP Tue Nov 12 09:22:33 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
After upgrading from node 13.1.0 to 13.2.0, after running
lerna
node doesn't exit normally but crashes:Steps to reproduce this bug: (you need
make
andyarn
)cc @addaleax (author of 55f98df, which introduced the assertion)
The text was updated successfully, but these errors were encountered: