Webpack-dev-server: SIGABRT

[antoinerousseau]

• Operating System:
• Node Version: 6.10.2
• NPM Version: 5.5.1
• webpack Version: 3.8.1
• webpack-dev-server Version: 2.9.3

• [x] This is a bug
• [ ] This is a feature request
• [ ] This is a modification request

Code

The dev server is started with this command, by Yarn 1.2.1:

webpack-dev-server -d --watch-poll --progress --port 5000 --history-api-fallback --open

Expected Behavior

The process should always keep running

Actual Behavior

The process sometimes (randomly) stops with an error:

error Command failed with signal "SIGABRT".

[shellscape]

@antoinerousseau this is likely caused by your configuration or environment. please try stack overflow or the webpack gitter for support. if you can identify an actual bug and culprit within webpack-dev-server, please let us know. closing as a question.

[jharris4]

I've been getting error Command failed with signal "SIGABRT". randomly lately as well. I haven't changed my configuration recently other than upgrading dependencies.

These are my webpack related package dependencies:

"webpack": "^3.8.1",
"webpack-bundle-analyzer": "^2.9.1",
"webpack-dev-middleware": "^1.12.2",
"webpack-hot-middleware": "^2.21.0"

And I'm running Node 9.21

[dorianmarie]

still happening, I get SIGABRT randomly

    "webpack": "^4.0.0",
    "webpack-assets-manifest": "*",
    "webpack-cli": "^3.0.0",
    "webpack-dev-server": "*",