cargdev/angular
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix(bazel): increase node memory limit for ng_module rule to prevent OOM for big modules (#28237)

Browse Source 
This came up as a request from an internal Google team.

Context:
- http://cl/229881085
- https://groups.google.com/a/google.com/forum/#!topic/nodejs/GLqDEOW0MV4

PR Close #28237
This commit is contained in:
Igor Minar 2019-01-18 07:47:48 -08:00 committed by Alex Rickabaugh
parent a0cdefb5fb
commit 73616ab237
1 changed files with 2 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
packages/bazel/src/ng_module.bzl
View File

@ -285,6 +285,8 @@ _EXTRA_NODE_OPTIONS_FLAGS = [
"--node_options=--expose-gc", "--node_options=--expose-gc",
# Show ~full stack traces, instead of cutting off after 10 items. # Show ~full stack traces, instead of cutting off after 10 items.
"--node_options=--stack-trace-limit=100", "--node_options=--stack-trace-limit=100",
# Give 2 GB RAM to node to make bigger google3 modules to compile, we should be able to drop this after Ivy/ngtsc is the default in g3
"--node_options=--max-old-space-size=2048",
] ]
def ngc_compile_action( def ngc_compile_action(