Webpack 3 seems to have/cause a memory leak

Do you want to request a feature or report a bug?

What is the current behavior?
webpack-dev-server crashes after ~30 mins of dev work (not sure how many cycles this constitutes, I’ll update with better estimates as I experience them). Specifically, I get FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - JavaScript heap out of memory.

I’m using webpack dashboard, which doesn’t let me copy + paste from the log window.
screen shot 2017-06-20 at 4 19 18 pm
screen shot 2017-06-20 at 4 19 25 pm

If the current behavior is a bug, please provide the steps to reproduce.

Non-deterministic. Sustained webpack-dev-server activity eventually throws a memory allocation exception, as described above.

What is the expected behavior?

Expected behaviour is for webpack-dev-server to continue to watch and rebuild app.

If this is a feature request, what is motivation or use case for changing the behavior?

Please mention other relevant information such as the browser version, Node.js version, webpack version and Operating System.

OS: macOS Sierra, v10.12.15. MBP, mid 2015, 2.5ghz i7, 16gb.
Node: 7.4.0
webpack-dev-server 2.4.5
webpack 3.0.0
browser: N/A

Author: Fantashit

2 thoughts on “Webpack 3 seems to have/cause a memory leak

  1. Had the same issue.

    I suggest you only use ModuleConcatenationPlugin only in production.

    In other words, disabling this plugin in dev environment will do the trick.

Comments are closed.