Visual Studio App Center CI构建React Native iOS应用遇堆内存不足问题

我之前也碰到过完全一样的坑，修改react-native-xcode.sh确实不靠谱——毕竟CI环境每次构建大概率会重新安装依赖，改好的脚本直接就被原始版本覆盖了。给你两个亲测有效的解决办法：

方法一：在App Center门户直接配置环境变量 #

这是最省心的方式，不需要改代码：

• 打开你的App Center项目，进入「Build」页面，选中你正在使用的iOS构建配置
• 切换到「Environment」标签页，点击「Add variable」
• 输入变量名NODE_OPTIONS，值填--expose-gc --max_old_space_size=32000
• 保存配置后，重新触发一次构建就行

方法二：通过appcenter-pre-build.sh脚本固化配置 #

如果想把配置同步到代码仓库里，就用这个方法：

1. 在项目根目录创建（或编辑）appcenter-pre-build.sh脚本，添加一行：

   export NODE_OPTIONS="--expose-gc --max_old_space_size=32000"
   

2. 给脚本加上执行权限，本地运行：

   chmod +x appcenter-pre-build.sh
   

3. 把这个脚本提交到代码仓库，App Center构建时会自动执行它，全局设置Node的内存参数

为什么之前修改react-native-xcode.sh没用？ #

核心原因有两个：

• CI环境里node_modules可能会被重新安装（比如每次构建都跑npm install），你修改的脚本会被覆盖
• React Native打包过程中，babel转换等耗内存的步骤是直接调用独立Node进程，这些进程不会读取你修改的react-native-xcode.sh里的参数，但会继承系统的NODE_OPTIONS环境变量

另外提一句：你用的Node 6.12.3版本确实比较老了，内存管理效率远不如新版本。如果项目允许的话，升级到Node 14+（React Native官方推荐版本），能从根源上减少内存溢出的概率。

附你提供的错误堆栈供参考：

transform[stdout]: <--- JS stacktrace ---
transform[stdout]:
transform[stdout]: ==== JS stack trace =========================================
transform[stdout]:
transform[stdout]: Security context: 0x194baa3cf781
transform[stdout]: 1: popContext [/Users/vsts/agent/2.127.0/work/1/s/node_modules/babel-traverse/lib/path/context.js:~222] [pc=0xb87791150c3] (this=0x399c406adfc9 <a NodePath with map 0x1b8e272b61a1>)
transform[stdout]: 2: visitQueue [/Users/vsts/agent/2.127.0/work/1/s/node_modules/babel-traverse/lib/context.js:~114] [pc=0xb8778a8efd2] (this=0xa337d831709 <a TraversalContext with map 0x1b8e272b5d81>,queue=0xa337d831751 <JS ...
transform[stdout]:
transform[stderr]: FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - JavaScript heap out of memory
transform[stderr]: 1: node::Abort() [/usr/local/Cellar/node@6/6.12.3/bin/node]
transform[stderr]: 2: node::FatalException(v8::Isolate*, v8::Localv8::Value, v8::Localv8::Message) [/usr/local/Cellar/node@6/6.12.3/bin/node]
transform[stderr]: 3: v8::Utils::ReportApiFailure(char const*, char const*) [/usr/local/Cellar/node@6/6.12.3/bin/node]
transform[stderr]: 4: v8::Utils::ApiCheck(bool, char const*, char const*) [/usr/local/Cellar/node@6/6.12.3/bin/node]
transform[stderr]: 5: v8::internal::V8::FatalProcessOutOfMemory(char const*, bool) [/usr/local/Cellar/node@6/6.12.3/bin/node]
transform[stderr]: 6: v8::internal::Factory::NewRawOneByteString(int, v8::internal::PretenureFlag) [/usr/local/Cellar/node@6/6.12.3/bin/node]
transform[stderr]: 7: v8::internal::Factory::NewStringFromOneByte(v8::internal::Vector, v8::internal::PretenureFlag) [/usr/local/Cellar/node@6/6.12.3/bin/node]
transform[stderr]: 8: v8::internal::Factory::NumberToString(v8::internal::Handlev8::internal::Object, bool) [/usr/local/Cellar/node@6/6.12.3/bin/node]
transform[stderr]: 9: v8::internal::Object::ToString(v8::internal::Isolate*, v8::internal::Handlev8::internal::Object) [/usr/local/Cellar/node@6/6.12.3/bin/node]
transform[stderr]: 10: v8::internal::Object::ConvertToName(v8::internal::Isolate*, v8::internal::Handlev8::internal::Object) [/usr/local/Cellar/node@6/6.12.3/bin/node]
transform[stderr]: 11: v8::internal::LookupIterator::PropertyOrElement(v8::internal::Isolate*, v8::internal::Handlev8::internal::Object, v8::internal::Handlev8::internal::Object, bool*, v8::internal::LookupIterator::Configuration) [/usr/local/Cellar/node@6/6.12.3/bin/node]
transform[stderr]: 12: v8::internal::Runtime::GetObjectProperty(v8::internal::Isolate*, v8::internal::Handlev8::internal::Object, v8::internal::Handlev8::internal::Object) [/usr/local/Cellar/node@6/6.12.3/bin/node]
transform[stderr]: 13: v8::internal::Runtime_KeyedGetProperty(int, v8::internal::Object**, v8::internal::Isolate*) [/usr/local/Cellar/node@6/6.12.3/bin/node]
transform[stderr]: 14: 0xb87779092a7
transform[stdout]:
transform[stdout]: <--- Last few GCs --->

内容的提问来源于stack exchange，提问作者Dinesh Chitta