Skip to content
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

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

Closed
r4wand opened this issue Mar 1, 2023 · 4 comments
Closed

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

r4wand opened this issue Mar 1, 2023 · 4 comments

Comments

@r4wand
Copy link

r4wand commented Mar 1, 2023

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

  • Clinic.js version: v12.0.0
  • Docter version: v10.0.0
  • Node.js version: v18.13.0

  • Operating system and version:
    Distributor ID: Ubuntu
    Description: Ubuntu 22.04.1 LTS
    Release: 22.04
    Codename: jammy

@r4wand r4wand changed the title Error: process exited by signal SIGABRT when doing ctrl+c Error: process exited by signal SIGABRT when doing ctrl+c or when server stops. Mar 1, 2023
@r4wand r4wand changed the title Error: process exited by signal SIGABRT when doing ctrl+c or when server stops. Error: process exited by signal SIGABRT when doing ctrl+c. Mar 1, 2023
@jonthomp
Copy link

jonthomp commented Mar 1, 2023

We are also experiencing this; I think it's probably a duplicate of #393

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

@r4wand
Copy link
Author

r4wand commented Mar 1, 2023

@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.

@r4wand r4wand closed this as completed Mar 1, 2023
@Jason5Lee
Copy link

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

@IslamWahid
Copy link

please add that to the docs

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants