Fix memory problems with webpack-dev-server in development mode #2433
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Before this webpack was using hashes in filenames for the generated files which are stored in memory. That meant on every change new files have been generated and stored in memory, quickly filling up the available memory. With this change we do not use hashes for filenames in development mode to avoid filling up memory.
|
LGTM. 👍 |
joschi
pushed a commit
that referenced
this pull request
Jun 29, 2016
Before this webpack was using hashes in filenames for the generated files which are stored in memory. That meant on every change new files have been generated and stored in memory, quickly filling up the available memory. With this change we do not use hashes for filenames in development mode to avoid filling up memory. Refs webpack/webpack#1914 (cherry picked from commit 3ab5918)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I am frequently running into webpack-dev-server memory problems in my development setup. Either my machine starts swapping or the node process dies with an out of memory error.
After some research I found a similar problem report in the webpack issue tracker. The problem is that our current dev setup uses hashes in filenames which means that on every change new files are built by webpack and served from memory. Since there is no mechanism to delete old ones, all files stay in memory and memory gets full eventually.
You can see this when you look at http://localhost:8080/webpack-dev-server. On every change to the javascript code, new files are appearing. In my case 104 files have been added on every change.
This change disables the usage of hashes in file names when running the webpack-dev-server in development mode. I have been running with this for one day and didn't run into any issues yet.