From 73616ab237eb163adecfee4ae5a1cae8f73d9c68 Mon Sep 17 00:00:00 2001 From: Igor Minar Date: Fri, 18 Jan 2019 07:47:48 -0800 Subject: [PATCH] fix(bazel): increase node memory limit for ng_module rule to prevent OOM for big modules (#28237) 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 --- packages/bazel/src/ng_module.bzl | 2 ++ 1 file changed, 2 insertions(+) diff --git a/packages/bazel/src/ng_module.bzl b/packages/bazel/src/ng_module.bzl index 9a4e651d40..8cb4639665 100644 --- a/packages/bazel/src/ng_module.bzl +++ b/packages/bazel/src/ng_module.bzl @@ -285,6 +285,8 @@ _EXTRA_NODE_OPTIONS_FLAGS = [ "--node_options=--expose-gc", # Show ~full stack traces, instead of cutting off after 10 items. "--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(