问题背景 #

我最近把React Native跨端项目（安卓+iOS）升级到了Expo SDK 54和react-native 0.81.4版本，安卓端用npx expo run:android连接USB设备运行完全没问题，但iOS端的情况就很头疼：不管是用npx expo run:ios启动iOS 18.3模拟器（平板和手机机型都试过），还是用EAS打包后在Expo Go里运行物理设备，都会偶现启动崩溃——有时候安装后启动一切正常，有时候刚启动就直接闪退，崩溃报告里核心错误是EXC_CRASH (SIGABRT)，还伴随多条mach_vm_allocate_kernel failed的内核内存分配失败提示。

完整崩溃报告 #

------------------------------------- Translated Report (Full Report Below) -------------------------------------
Incident Identifier: 89AC698E-6E14-4088-810F-256E51B8E6D1
CrashReporter Key: 7BC5BDB1-7A7E-54C4-9C3D-1CBA647DACF4
Hardware Model: Mac14,3
Process: easyTeleMed [61418]
Path: /Users/USER/Library/Developer/CoreSimulator/Devices/8BF70FBE-6C23-442A-A685-CC29E3AEA10A/data/Containers/Bundle/Application/DEBF2FE0-0AAD-4855-B54C-FFE15C54090C/easyTeleMed.app/easyTeleMed
Identifier: it.ingeniars.easytelemed
Version: 1.0.3 (4)
Code Type: ARM-64 (Native)
Role: Foreground
Parent Process: launchd_sim [57370]
Coalition: com.apple.CoreSimulator.SimDevice.8BF70FBE-6C23-442A-A685-CC29E3AEA10A [1660468]
Responsible Process: SimulatorTrampoline [14608]
Date/Time: 2025-09-26 17:55:05.5902 +0200
Launch Time: 2025-09-26 17:55:03.3177 +0200
OS Version: macOS 14.5 (23F79)
Release Type: User
Report Version: 104

Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Termination Reason: SIGNAL 6 Abort trap: 6
Terminating Process: easyTeleMed [61418]
Triggered by Thread: 27

Kernel Triage:
VM - (arg = 0x3) mach_vm_allocate_kernel failed within call to vm_map_enter
VM - (arg = 0x3) mach_vm_allocate_kernel failed within call to vm_map_enter
VM - (arg = 0x3) mach_vm_allocate_kernel failed within call to vm_map_enter
VM - (arg = 0x3) mach_vm_allocate_kernel failed within call to vm_map_enter
VM - (arg = 0x3) mach_vm_allocate_kernel failed within call to vm_map_enter

Thread 0:
0 libsystem_kernel.dylib 0x1054a9570 0x1054a8000 + 5488
1 libsystem_kernel.dylib 0x1054b1798 0x1054a8000 + 38808
2 libsystem_kernel.dylib 0x1054a98e8 0x1054a8000 + 6376
3 CoreFoundation 0x18041cae0 0x18038d000 + 588512
4 CoreFoundation 0x180417008 0x18038d000 + 565256
5 CoreFoundation 0x180416704 0x18038d000 + 562948
6 GraphicsServices 0x190604b10 0x190601000 + 15120
7 UIKitCore 0x185b39180 0x184cd9000 + 15073664
8 UIKitCore 0x185b3d378 0x184cd9000 + 15090552
9 easyTeleMed.debug.dylib 0x107089354 __debug_main_executable_dylib_entry_point + 64 (AppDelegate.swift:6)
10 dyld_sim 0x104fdd410 0x104fdc000 + 5136
11 dyld 0x1049560e0 0x104950000 + 24800

Thread 1:
0 libsystem_pthread.dylib 0x104eda5cc 0x104ed8000 + 9676

Thread 2:
0 libsystem_pthread.dylib 0x104eda5cc 0x104ed8000 + 9676

Thread 3:
0 CoreFoundation 0x180444a68 0x18038d000 + 752232
1 CoreFoundation 0x1804543b8 0x18038d000 + 816056
2 CoreFoundation 0x1804468b8 0x18038d000 + 759992
3 CoreFoundation 0x1803d85a8 0x18038d000 + 308648
4 CoreFoundation 0x1803d8408 0x18038d000 + 308232
5 Foundation 0x180e646e4 0x1807da000 + 6858468
6 Foundation 0x180ef6e6c 0x1807da000 + 7458412
7 libsystem_trace.dylib 0x1800a67b0 0x1800a4000 + 10160
8 libsystem_trace.dylib 0x1800a603c 0x1800a4000 + 8252
9 libsystem_trace.dylib 0x1800b51f4 0x1800a4000 + 70132
10 libsystem_trace.dylib 0x1800b4a3c 0x1800a4000 + 68156
11 libsystem_trace.dylib 0x1800b76c0 0x1800a4000 + 79552
12 CFNetwork 0x1849a9be8 0x184800000 + 1743848
13 CFNetwork 0x18481f6e4 0x184800000 + 128740
14 CFNetwork 0x18480db08 0x184800000 + 56072
15 CFNetwork 0x18480daf8 0x184800000 + 56056
16 CFNetwork 0x184a271e4 0x184800000 + 2257380
17 CFNetwork 0x18481cf28 0x184800000 + 118568
18 CFNetwork 0x1849cb1a8 0x184800000 + 1880488
19 CFNetwork 0x1849ca820 0x184800000 + 1878048
20 CFNetwork 0x184885168 0x184800000 + 545128
21 CFNetwork 0x184884c28 0x184800000 + 543784
22 CFNetwork 0x184884f3c 0x184800000 + 544572
23 CFNetwork 0x184884c28 0x184800000 + 543784
24 CFNetwork 0x1848844ac 0x184800000 + 541868
25 CFNetwork 0x18496f864 0x184800000 + 1505380
26 CFNetwork 0x184887990 0x184800000 + 555408
27 libdispatch.dylib 0x18018c610 0x180179000 + 79376
28 libdispatch.dylib 0x18017cc08 0x180179000 + 15368
29 libdispatch.dylib 0x180184da0 0x180179000 + 48544
30 libdispatch.dylib 0x180185924 0x180179000 + 51492
31 libdispatch.dylib 0x180191038 0x180179000 + 98360
32 libdispatch.dylib 0x180190694 0x180179000 + 95892
33 libsystem_pthread.dylib 0x104edb814 0x104ed8000 + 14356
34 libsystem_pthread.dylib 0x104eda5d4 0x104ed8000 + 9684

Thread 4:
0 libsystem_pthread.dylib 0x104eda5cc 0x104ed8000 + 9676

Thread 5:
0 libsystem_pthread.dylib 0x104eda5cc 0x104ed8000 + 9676

Thread 6:
0 libsystem_pthread.dylib 0x104eda5cc 0x104ed8000 + 9676

Thread 7:: com.apple.uikit.eventfetch-thread

排查与解决建议 #

我之前帮朋友排查过类似的偶现崩溃问题，结合这份报告给你几个优先级高的排查方向：

1. 先解决模拟器/系统资源问题 #

从报告里的mach_vm_allocate_kernel failed能明确看出是内核级内存分配失败，iOS 18.3模拟器本身可能存在资源泄漏的小bug，先试试这些快速缓解的操作：

• 彻底重置模拟器：打开模拟器后选择Hardware > Erase All Content and Settings，清空所有数据后再重新运行项目
• 清理Mac内存：关闭其他占用CPU/内存高的应用（比如视频剪辑、大型游戏），释放系统资源后再启动项目
• 换iOS版本测试：暂时切换到iOS 18.2模拟器，看崩溃是否消失，确认是不是iOS 18.3的特定兼容性问题

2. 排查Expo SDK 54的依赖冲突 #

SDK 54刚发布不久，部分第三方原生模块还没适配react-native 0.81.x：

• 检查package.json里的原生依赖（比如相机、存储、网络相关的社区库），优先更新到官方标注支持SDK 54的版本
• 尝试创建一个干净的SDK 54空白项目，逐步迁移你的核心代码，看添加到哪个模块时出现崩溃，精准定位问题依赖

3. 检查启动阶段的异步逻辑 #

偶现崩溃大概率和启动时的异步任务竞争有关，报告里崩溃触发点指向AppDelegate.swift:6，可以重点检查：

• 打开AppDelegate.swift，看启动阶段有没有执行初始化第三方SDK、读取本地存储这类异步操作，添加异常捕获或者延迟执行逻辑
• 把非必要的初始化代码从启动流程中移除，放到App完全启动后（比如首页渲染完成）再执行

4. 修复EAS打包/预构建缓存问题 #

如果是打包后才出现的崩溃，可能是缓存导致的原生代码不一致：

• 执行npx expo prebuild --clean清理原生目录后重新预构建，再运行iOS项目
• 检查eas.json里的iOS生产环境配置，暂时关闭minifyEnabled这类代码优化选项，看崩溃是否消失

如果以上步骤都没解决，建议去Expo官方GitHub Issues搜SDK 54 iOS 18.3 crash，大概率能找到其他开发者遇到的类似情况和官方给出的临时补丁方案。