Describe the issue
If you are running Hardhat 3 and its process crashes after Hardhat already finished running, you are probably affected by this Node.js issue.
If that’s the case, please upgrade to Node 24.13.1 or above, including any Node 26.x version. We’d appreciate if you can also add a comment here describing your setup.
Please note that this issue is related to actual process crashes due to data race and use-after-free in Node.js’ napi_threadsafe_function, not unhandled exceptions. You can identify these crashes by errors such as Segmentation fault, SIGSEGV, SIGABRT, Illegal instruction, core dumped, or native stack traces involving Node.js, V8, or native dependencies.
JavaScript errors like Uncaught Error: ..., UnhandledPromiseRejection, assertion failures, or regular stack traces pointing to your code are not caused by this Node.js issue.
Describe the issue
If you are running Hardhat 3 and its process crashes after Hardhat already finished running, you are probably affected by this Node.js issue.
If that’s the case, please upgrade to Node 24.13.1 or above, including any Node 26.x version. We’d appreciate if you can also add a comment here describing your setup.
Please note that this issue is related to actual process crashes due to data race and use-after-free in Node.js’
napi_threadsafe_function, not unhandled exceptions. You can identify these crashes by errors such asSegmentation fault,SIGSEGV,SIGABRT,Illegal instruction,core dumped, or native stack traces involving Node.js, V8, or native dependencies.JavaScript errors like
Uncaught Error: ...,UnhandledPromiseRejection, assertion failures, or regular stack traces pointing to your code are not caused by this Node.js issue.