Webpack-dev-server: Frequent crashes with `Command failed with exit code 134.`

[EvHaus]

What is the current behavior?

After running for a few hours, webpack-server-dev is often crashing for me and my colleagues with the following error:

sh: line 1: 26853 Abort trap: 6           webpack-dev-server --hot --progress --history-api-fallback --config webpack/webpack.dev.config.js --content-base html/
error Command failed with exit code 134.

There is no other output and we haven't yet been able to determine what's causing it. it seems to be fairly random, but consistent.

Our project is about 3000-4000 modules large.

What is the expected behavior?

No crash. Or better error message explaining what the issue was.

Please mention your webpack and Operating System version.

Mac OSX 10.12.4

webpack: 2.5.1
webpack-dev-server: 2.4.5

[shellscape]

Closing due to age and inactivity. We'd happily review a pull request if you happen to find a solution, but this one definitely looks like an edge case. I'd suggest using a tool like forever to ensure it recovers from a crash in the meantime.

[EvHaus]

Can you give any more insight into what Command failed with exit code 134. means? I don't know where to start to dig into this deeper.

[Marindrew]

Having the same issue, webpack version 3.10.0, os x 10.13.3

[williamvasquezladders]

On the same boat. Webpack Version 3.10.0 os x 10.12.6

[leon-yum]

I'm getting this now :(

This started happening recently...

OSX 10.12.6
webpack ^3.3.0
webpack-dev-server ^2.9.4

Child html-webpack-plugin for "index.html":
     1 asset
       4 modules
webpack: Compiled successfully.
sh: line 1: 25436 Abort trap: 6           webpack-dev-server --colors
error An unexpected error occurred: "Command failed.
Exit code: 134
Command: sh
Arguments: -c webpack && webpack-dev-server --colors
Directory: /Users/leongaban/projects/go/src/github.com/pizzahutdigital/mythor
Output:
".
info If you think this is a bug, please open a bug report with the information provided in "/Users/leongaban/projects/go/src/github.com/pizzahutdigital/mythor/yarn-error.log".
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

[QoT]

I have the same error message when trying to use yarn so it probably is not related specifically to webpack.

Vedrans-Mac-mini:tensorflow.js-classifier vedrano$ yarn watch
yarn run v1.12.1
$ cross-env NODE_ENV=development parcel index.html --no-hmr --open
Server running at http://localhost:1234
⠦ Building index-nonode.js...
<--- Last few GCs --->
...
/var/folders/dc/kt06jl4n17393wmd8xmqtcsr0000gn/T/yarn--1541874315534-0.04599513967422797/node: line 3: 4868 Abort trap: 6 "/usr/local/Cellar/node/11.1.0/bin/node" "$@"
error Command failed with exit code 134.

[willthemoor]

I have the same error message when trying to use yarn so it probably is not related specifically to webpack.

Searching brought me here. Thought I'd leave a note confirming what @QoT said for future landers. It's not related specifically to webpack. I'm researching the same error but I'm not using webpack.

[imirza10]

And I am getting this information: The command "grunt.cmd --no-color default" exited with code 134.
So I endorse @willthemoor, its not only the WebPack error apparently

[ahmad-ali14]

https://stackoverflow.com/a/56135994/10871748

adding a specific node and npm version, similar to my local env has solved the proplem

// in package.json

"engines": {
    "node": "12.6.0",
    "npm": "6.14.4"
  },

[pnoken]

<--- Last few GCs --->

[21816:0000029E47DA1E20] 173246 ms: Mark-sweep (reduce) 2042.2 (2051.2) -> 2041.4 (2052.4) MB, 4042.1 / 1.2 ms (average mu = 0.067, current mu = 0.006) allocation failure scavenge might not succeed
[21816:0000029E47DA1E20] 177915 ms: Mark-sweep (reduce) 2042.5 (2054.4) -> 2041.7 (2054.7) MB, 4592.0 / 1.2 ms (average mu = 0.040, current mu = 0.016) allocation failure scavenge might not succeed

<--- JS stacktrace --->

FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
1: 00007FF76084058F napi_wrap+109311
2: 00007FF7607E52B6 v8::internal::OrderedHashTable::NumberOfElementsOffset+33302
3: 00007FF7607E6086 node::OnFatalError+294
4: 00007FF7610B150E v8::Isolate::ReportExternalAllocationLimitReached+94
5: 00007FF76109638D v8::SharedArrayBuffer::Externalize+781
6: 00007FF760F4081C v8::internal::Heap::EphemeronKeyWriteBarrierFromCode+1516
7: 00007FF760F4BB5A v8::internal::Heap::ProtectUnprotectedMemoryChunks+1258
8: 00007FF760F48D09 v8::internal::Heap::PageFlagsAreConsistent+2457
9: 00007FF760F3D931 v8::internal::Heap::CollectGarbage+2033
10: 00007FF760F3BB35 v8::internal::Heap::AllocateExternalBackingStore+1317
11: 00007FF760F55DD6 v8::internal::Factory::AllocateRaw+166
12: 00007FF760F697F4 v8::internal::FactoryBase::NewFixedArrayWithFiller+84
13: 00007FF760F69745 v8::internal::FactoryBase::NewFixedArray+69
14: 00007FF760E36112 v8::Object::GetIsolate+52802
15: 00007FF760E35472 v8::Object::GetIsolate+49570
16: 00007FF760DBA7B6 v8::internal::LayoutDescriptor::Trim+20038
17: 00007FF760DB6318 v8::internal::LayoutDescriptor::Trim+2472
18: 00007FF760DB9C18 v8::internal::LayoutDescriptor::Trim+17064
19: 00007FF760DB9898 v8::internal::LayoutDescriptor::Trim+16168
20: 00007FF760C9B8C3 v8::internal::interpreter::JumpTableTargetOffsets::iterator::operator=+65171
21: 00007FF760C9BC17 v8::internal::interpreter::JumpTableTargetOffsets::iterator::operator=+66023
22: 00007FF761139EBD v8::internal::SetupIsolateDelegate::SetupHeap+463949
23: 00000241E40F2CF8
error Command failed with exit code 134.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.