which product (packages/*): @google-cloud/resource-manager
OS: macosx
Node.js version: v18.14.2
npm version: 8
google-cloud-node version: 4.3.0
Steps to reproduce
If you use the google-cloud/resource-manager and then also implement shutdown hooks within your application that gracefully stop things like a webserver, before doing a process.exit(0); then you end up with a SIGABRT:
❯ NODE_OPTIONS="--trace-events-enabled --trace-event-categories v8" node test.js
hi
hi
hi
hi
hi
^C[1] 55453 abort NODE_OPTIONS="--trace-events-enabled --trace-event-categories v8" node test.j
Environment details
Steps to reproduce
If you use the
google-cloud/resource-manager
and then also implement shutdown hooks within your application that gracefully stop things like a webserver, before doing aprocess.exit(0)
; then you end up with aSIGABRT
:This code reproduces the issue: