clinicjs / node-clinic

Clinic.js diagnoses your Node.js performance issues
https://clinicjs.org
MIT License
5.69k stars 125 forks source link

`Error: process exited by signal SIGABRT` when doing `ctrl+c`. #396

Closed r4wand closed 1 year ago

r4wand commented 1 year ago

Expected Behavior

I am expecting clinic.js to stop listing and start generating the HTML report files.

Current Behavior

When I do ctrl+c I get the following error. Error: process exited by signal SIGABRT at ChildProcess.<anonymous> (/home/rawand/.nvm/versions/node/v18.13.0/lib/node_modules/clinic/node_modules/@clinic/doctor/index.js:133:13) at Object.onceWrapper (node:events:628:26) at ChildProcess.emit (node:events:513:28) at ChildProcess._handle.onexit (node:internal/child_process:291:12)

Steps to Reproduce (for bugs)

clone the sample clinic's repository. git clone git@github.com:nearform/node-clinic-doctor-examples.git cd node-clinic-doctor-examples npm i

then start clinic clinic doctor --on-port 'autocannon localhost:$PORT' -- node slow-event-loop

Sample upload

Environment

jonthomp commented 1 year ago

We are also experiencing this; I think it's probably a duplicate of https://github.com/clinicjs/node-clinic/issues/393

If you are able to upgrade, it looks like 19 solves the problem

r4wand commented 1 year ago

@jonthomp Thank you, updating to Node.js v19.7.0 fixed it. I'll close this issue as it's pretty much the same issue as the one you mentioned.

Jason5Lee commented 1 year ago

I have to use Node.js v18 for some specific reasons. Is there any workaround available?

IslamWahid commented 1 year ago

please add that to the docs