You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Linux u24vm 6.8.0-50-generic #51-Ubuntu SMP PREEMPT_DYNAMIC Sat Nov 9 17:58:29 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux
Subsystem
async_hooks
What steps will reproduce the bug?
Setup a node instance,
» node
and run the following javascript code.
class ASYNC_HOOKS_TEST {}
async_hooks = require('async_hooks');
_38 = async_hooks.createHook({init:ASYNC_HOOKS_TEST});
_38.enable();
Then the node instance occurs an abort.
How often does it reproduce? Is there a required condition?
This abort can always be triggered following the steps above.
What is the expected behavior? Why is that the expected behavior?
If any error occurs, an exception or other similar error-reporting stuff should be thrown and then caught and handled correctly. There is no reason to abort the whole node process.
The text was updated successfully, but these errors were encountered:
zyscoder
changed the title
Running initAsyncResource with a class constructor leads to an exception, which is not catched and results in the server's abort
Running initAsyncResource with a class constructor results in an abort
Dec 25, 2024
Version
v22.11.0
Platform
Subsystem
async_hooks
What steps will reproduce the bug?
Setup a node instance,
and run the following javascript code.
Then the node instance occurs an abort.
How often does it reproduce? Is there a required condition?
This abort can always be triggered following the steps above.
What is the expected behavior? Why is that the expected behavior?
If any error occurs, an exception or other similar error-reporting stuff should be thrown and then caught and handled correctly. There is no reason to abort the whole node process.
What do you see instead?
Additional information
No response
The text was updated successfully, but these errors were encountered: