Document / warn about RAM usage, OOM Errors #50
Comments
|
Thanks for opening this issue. Do you mind opening a PR with where you think this argument should be in the scripts, or adding a note in the README? |
opyh
added a commit
to opyh/meteor-base
that referenced
this issue
Jun 12, 2020
Meteor’s source map generation uses no GC, which can produce out-of-memory errors in CI environments with <4G RAM. If this happens, the reason for killed containers can be difficult to track down. Some environments display a ‘OOMError’, some show a cryptic error message (‘non-zero exit code 137’), some show no error at all. This adds a warning so you have a clue from the logs when the container is killed. Related Meteor issue: meteor/meteor#9568
opyh
added a commit
to opyh/meteor-base
that referenced
this issue
Jun 12, 2020
Meteor’s source map generation uses no GC, which can produce out-of-memory errors in CI environments with <4G RAM. If this happens, the reason for killed containers can be difficult to track down. Some environments display a ‘OOMError’, some show a cryptic error message (‘non-zero exit code 137’), some show no error at all. This adds a warning so you have a clue from the logs when the container is killed. Related Meteor issue: meteor/meteor#9568
|
Here it is :) |
GeoffreyBooth
added a commit
that referenced
this issue
Dec 30, 2020
Add OOM error warning to build script; resolves #50
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hey @GeoffreyBooth, thanks for your efforts on this project!
This issue is mainly to help people googling for these keyword: OOM, out-of-memory, non-zero exit code 137 error, aborted build.
You might be affected by meteor/meteor#9568.
meteor buildcan use more RAM than you expect. Setting--max-old-space-size=2048or similar options for Node won't help (as of Meteor 1.10.2), as the source maps generation is currently using wasm and explicitly switches off GC to mitigate another issue innode-fibers.This issue is frustrating to find in CI setups, where the container is usually just stopped - not all environments display a sensible error message for out-of-memory errors.
Potential solutions: meteor/meteor#9568 (comment)
I don't know if Meteor will adopt my suggestion from meteor/meteor#9568 (comment) - but if not, it might be a good idea to add it to this image's build scripts :)
The text was updated successfully, but these errors were encountered: