Add more info about OOM build failiure [docs] #2060
Merged
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.
In the section about npm run build fails in troubleshooting added more
info about memory usage of the build script and a link to a tutorial for
adding more swap space as a viable solution.
Today I tried to create a build in my cheap 512MB Digital Ocean
Ubuntu server and I ran into issues similar to #1026 and #1493.
After running the command while having the system monitor open, I
noticed that it uses hundreds of megabytes of memory. The
docs do mention this issue, but what really helped me was a tutorial
that I found online for adding more swap space to the server. It is for
Ubuntu 14.04 but it does work on newer versions and it should be still
useful for any other Linux distro that uses systemd. I think that it would
be good to add it to the docs.
Also, since #1496 it no longer fails silently, so I decided to change the title
accordingly along with the console message so that users can easily find it.