-
Notifications
You must be signed in to change notification settings - Fork 465
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
SIGABRT under debug build (node_g) only #722
Comments
Just taking a |
Can't seem to repro it in the tests - might be in worker cleanup |
Are the tests supposed to pass under
|
The isolate check is in node ( |
I think its likely related to the discussion in this issue: nodejs/node#33276, the issue under debug. |
@davedoesdev sounds like you are trying to create a small repo, that would be useful. |
@mhdawson see https://github.com/davedoesdev/node-addon-api/commit/db69c2268c6533d1d4fdd07b3191e0a5cf38f3c9 The new test fails under |
@davedoesdev I assume you meant debug when you said node_g but not so sure anymore. Is that what you meant or something else? |
Yes, BUILDTYPE=Debug |
Refs: nodejs/node-addon-api#722 Ensure a scope is on stack during finalization as finalization functions can create JS Objects Signed-off-by: Michael Dawson <michael_dawson@ca.ibm.com>
This issue has the same root cause as #730. |
Refs: nodejs/node-addon-api#722 Ensure a scope is on stack during finalization as finalization functions can create JS Objects Signed-off-by: Michael Dawson <michael_dawson@ca.ibm.com> PR-URL: #33508 Reviewed-By: Gabriel Schulhof <gabriel.schulhof@intel.com> Reviewed-By: James M Snell <jasnell@gmail.com>
Refs: nodejs/node-addon-api#722 Ensure a scope is on stack during finalization as finalization functions can create JS Objects Signed-off-by: Michael Dawson <michael_dawson@ca.ibm.com> PR-URL: nodejs#33508 Reviewed-By: Gabriel Schulhof <gabriel.schulhof@intel.com> Reviewed-By: James M Snell <jasnell@gmail.com>
Refs: nodejs/node-addon-api#722 Ensure a scope is on stack during finalization as finalization functions can create JS Objects Signed-off-by: Michael Dawson <michael_dawson@ca.ibm.com> PR-URL: #33508 Reviewed-By: Gabriel Schulhof <gabriel.schulhof@intel.com> Reviewed-By: James M Snell <jasnell@gmail.com>
Refs: nodejs/node-addon-api#722 Ensure a scope is on stack during finalization as finalization functions can create JS Objects Signed-off-by: Michael Dawson <michael_dawson@ca.ibm.com> PR-URL: #33508 Reviewed-By: Gabriel Schulhof <gabriel.schulhof@intel.com> Reviewed-By: James M Snell <jasnell@gmail.com>
Refs: nodejs/node-addon-api#722 Ensure a scope is on stack during finalization as finalization functions can create JS Objects Signed-off-by: Michael Dawson <michael_dawson@ca.ibm.com> PR-URL: nodejs#33508 Reviewed-By: Gabriel Schulhof <gabriel.schulhof@intel.com> Reviewed-By: James M Snell <jasnell@gmail.com>
Refs: nodejs/node-addon-api#722 Ensure a scope is on stack during finalization as finalization functions can create JS Objects Signed-off-by: Michael Dawson <michael_dawson@ca.ibm.com> PR-URL: #33508 Reviewed-By: Gabriel Schulhof <gabriel.schulhof@intel.com> Reviewed-By: James M Snell <jasnell@gmail.com>
Refs: nodejs/node-addon-api#722 Ensure a scope is on stack during finalization as finalization functions can create JS Objects Signed-off-by: Michael Dawson <michael_dawson@ca.ibm.com> PR-URL: #33508 Reviewed-By: Gabriel Schulhof <gabriel.schulhof@intel.com> Reviewed-By: James M Snell <jasnell@gmail.com>
I see some commits have been made in nodejs related to this issue. Should this be fixed? |
@davedoesdev the changes were landed in mater and have been backported to 14.x and 12.x as well so it should be fixed for those versions. |
Thanks, yes it appears to be fixed. |
Add test for ObjectWrap destructor (no HandleScope exception) REFS: nodejs/node-addon-api#722 PR-URL: nodejs/node-addon-api#729 Reviewed-By: Michael Dawson <michael_dawson@ca.ibm.com>
Add test for ObjectWrap destructor (no HandleScope exception) REFS: nodejs/node-addon-api#722 PR-URL: nodejs/node-addon-api#729 Reviewed-By: Michael Dawson <michael_dawson@ca.ibm.com>
Add test for ObjectWrap destructor (no HandleScope exception) REFS: nodejs/node-addon-api#722 PR-URL: nodejs/node-addon-api#729 Reviewed-By: Michael Dawson <michael_dawson@ca.ibm.com>
Add test for ObjectWrap destructor (no HandleScope exception) REFS: nodejs/node-addon-api#722 PR-URL: nodejs/node-addon-api#729 Reviewed-By: Michael Dawson <michael_dawson@ca.ibm.com>
Cause is "Cannot create a handle without a HandleScope" because
~ObjectWrap()
callsValue()
without a taking aHandleScope
.Stack trace:
The text was updated successfully, but these errors were encountered: