在构建 CodePush 时接收内存中的 javascript 堆Microsoft

Question

我只在构建 CodePush 发行版时收到此错误。

$appcenter codepush release-react -a APPNAME.com/APPNAME-ios -d Production --mandatory --output-dir ./build -t 1.x.x;
transform[stderr]: FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
transform[stderr]: 
transform[stderr]: Writing Node.js report to file: report.20191010.093411.22661.001.json
transform[stderr]: Node.js report completed
transform[stderr]:  1: 0x100062df2 node::Abort() [/usr/local/bin/node]
transform[stderr]:  2: 0x1000634eb node::OnFatalError(char const*, char const*) [/usr/local/bin/node]
transform[stderr]:  3: 0x1001aeda7 v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, bool) [/usr/local/bin/node]
transform[stderr]:  4: 0x1001aed44 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, bool) [/usr/local/bin/node]
transform[stderr]:  5: 0x1005b5bd2 v8::internal::Heap::FatalProcessOutOfMemory(char const*) [/usr/local/bin/node]
transform[stderr]:  6: 0x1005b8103 v8::internal::Heap::CheckIneffectiveMarkCompact(unsigned long, double) [/usr/local/bin/node]
transform[stderr]:  7: 0x1005b4638 v8::internal::Heap::PerformGarbageCollection(v8::internal::GarbageCollector, v8::GCCallbackFlags) [/usr/local/bin/node]
transform[stderr]:  8: 0x1005b27f5 v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [/usr/local/bin/node]
transform[stderr]:  9: 0x1005bf09c v8::internal::Heap::AllocateRawWithLightRetry(int, v8::internal::AllocationSpace, v8::internal::AllocationAlignment) [/usr/local/bin/node]
transform[stderr]: 10: 0x1005bf11f v8::internal::Heap::AllocateRawWithRetryOrFail(int, v8::internal::AllocationSpace, v8::internal::AllocationAlignment) [/usr/local/bin/node]
transform[stderr]: 11: 0x10058e314 v8::internal::Factory::NewFillerObject(int, bool, v8::internal::AllocationSpace) [/usr/local/bin/node]
transform[stderr]: 12: 0x100840c54 v8::internal::Runtime_AllocateInNewSpace(int, v8::internal::Object**, v8::internal::Isolate*) [/usr/local/bin/node]
transform[stderr]: 13: 0x23da4894fc7d

如何告诉应用中心使用max_old_space_size=8192？

Answer 1

这说明了问题的解决方案。

在 Android 上，将以下内容添加到项目的 build.gradle 文件中：

project.ext.react = [
nodeExecutableAndArgs: ["node", "--max_old_space_size=8192"]
]

在 iOS 的 Xcode 中，选择您的目标并转到"构建阶段"选项卡， 在捆绑 React Native 代码和图像部分中，将标志添加到 外壳脚本：

export NODE_BINARY="'node --max_old_space_size=8192'
../node_modules/react-native/packager/react-native-xcode.sh"

希望这有帮助！

Answer 2

将它们添加到脚本中，然后按顺序运行它们。

"setup-fix-memory-limit": "npm install -g increase-memory-limit",
"fix-memory-limit": "cross-env LIMIT=4096 increase-memory-limit",

将第二个脚本中的数字更改为您想要的数字。

npm run setup-fix-memory-limit
npm run fix-memory-limit

还要确保查看是否可以以其他方式解决，也许一些不正确的导入会大大增加捆绑包的大小，使用捆绑分析器查看构建中的内容是否应该是他们的，或者是否可以修剪任何东西。

Answer 3

这里讨论了类似的问题。您可以尝试运行此 react-native bundle 命令：

node --expose-gc --max_old_space_size=8192 ./node_modules/react-native/local-cli/cli.js bundle --entry-file='index.js' --bundle-output='./ios/main.jsbundle' --dev=false --platform='ios' --assets-dest='./ios'

Answer 4

我在Bitrise上运行代码推送时遇到了同样的问题。通过将其导出到CODE_PUSH_NODE_ARGS环境变量上来解决。

export CODE_PUSH_NODE_ARGS='--max_old_space_size=8192'
appcenter codepush release-react ...