CococaPods：pod install 导致机器崩溃

如何解决CococaPods：pod install 导致机器崩溃

在我的 react-native 项目中，由于某些版本冲突，我确实删除了 Podfile.lock 和 Pods 文件夹以重新安装它们。使用两种流动方法安装 Pod

1. pod install 在 ios 文件夹中有或没有 --repo-update 标志
2. bundle exec pod install --repo-update --project-directory=ios/ 在 根，

进程卡在 generating pods project， 系统变慢，几分钟后系统关闭 关闭/重新启动。 我应该如何排查问题？

此外，如果 VSCode 处于打开状态，code helper (renderer) 也会在 pod install 开始时消耗高百分比的 cpu

System:
    OS: macOS 11.3
    cpu: (8) x64 Intel(R) Core(TM) i5-8257U cpu @ 1.40GHz
    Memory: 308.68 MB / 8.00 GB
    Shell: 5.8 - /bin/zsh
  Binaries:
    Node: 14.15.4 - ~/.nvm/versions/node/v14.15.4/bin/node
    Yarn: 2.4.0 - ~/<projectPath>/node_modules/.bin/yarn
    npm: 6.14.10 - ~/.nvm/versions/node/v14.15.4/bin/npm
    Watchman: 4.9.0 - /usr/local/bin/watchman
  Managers:
    CocoaPods: 1.10.1 - /Users/amir/.rvm/gems/ruby-2.7.0/bin/pod
  SDKs:
    iOS SDK:
      Platforms: iOS 14.4,DriverKit 20.2,macOS 11.1,tvOS 14.3,watchOS 7.2
    Android SDK:
      API Levels: 23,25,26,27,28,29
      Build Tools: 27.0.3,28.0.3,29.0.2
      System Images: android-26 | Intel x86 Atom,android-26 | Intel x86 Atom_64,android-26 | Google Apis Intel x86 Atom,android-26 | Google Apis Intel x86 Atom_64,android-27 | Google Apis Intel x86 Atom,android-27 | Google Play Intel x86 Atom,android-28 | Intel x86 Atom,android-28 | Intel x86 Atom_64,android-28 | Google Apis Intel x86 Atom,android-28 | Google Apis Intel x86 Atom_64,android-28 | Google Play Intel x86 Atom,android-28 | Google Play Intel x86 Atom_64,android-30 | Google Apis Intel x86 Atom
      Android NDK: Not Found
  IDEs:
    Android Studio: 4.0 AI-193.6911.18.40.6626763
    Xcode: 12.4/12D4e - /usr/bin/xcodebuild
  Languages:
    Java: 11.0.2 - /Users/amir/.sdkman/candidates/java/current/bin/javac
  npmPackages:
    @react-native-community/cli: Not Found
    react: 17.0.1 => 17.0.1
    react-native: 0.64.0 => 0.64.0
    react-native-macos: Not Found
  npmGlobalPackages:
    *react-native*: Not Found

解决方法

这是脚蹼问题 我在这里找到了解决方案 运行 --verbose 向我展示了导致问题的库，https://github.com/facebook/flipper/issues/2248#issuecomment-830060572 修复了它