Issue Description
The OpenAgents Launcher (v0.8.1) crashes immediately on launch on macOS 26.5 (build 25F71). The app shows no UI and exits with code 133.
Environment
| Item |
Value |
| macOS |
26.5 (build 25F71) |
| Hardware |
Apple Silicon (arm64), Mac16,10 |
| RAM |
16 GB |
| App Version |
0.8.1 |
| Electron Version |
33.4.11 |
| Architecture |
arm64 native |
| App Build SDK |
macOS 14.5 (Xcode 15.4) |
Error Output
Running the executable directly:
Fatal process out of memory: Failed to reserve virtual memory for CodeRange
Crash type: EXC_BREAKPOINT / SIGTRAP in v8::Isolate::Initialize()
Full crash log excerpt (from ~/Library/Logs/DiagnosticReports/):
- exception:
EXC_BREAKPOINT, signal SIGTRAP
- termination:
Trace/BPT trap: 5, by exc handler
- faulting thread: main thread, frame 0 in
v8::Isolate::Initialize
- procLaunch → procExit: ~55ms (instant crash)
Root Cause Analysis
The Electron framework is compiled against the macOS 14.5 SDK. macOS 26.5 appears to have changed how MAP_JIT memory reservations work for V8 JIT compilation (the CodeRange region). The mmap call for the JIT code area fails during V8 isolate initialization, causing an immediate fatal crash before any UI renders.
This is not a physical memory shortage — the crash persists even with 8+ GB of free RAM.
Steps to Reproduce
- Install OpenAgents Launcher v0.8.1 on macOS 26.5 (Apple Silicon)
- Double-click the app or run from terminal
- App crashes instantly with no UI
Things I Already Tried
Suggested Fix
Rebuild the Electron app with a newer macOS SDK (≥ the current macOS 26 SDK) so that the Electron/V8 binary is compatible with the updated MAP_JIT memory allocation behavior on macOS 26.5. This likely requires updating the Electron version used in the build pipeline.
Crash Report
Full .ips crash log is available in ~/Library/Logs/DiagnosticReports/ — happy to attach if needed.
Issue Description
The OpenAgents Launcher (v0.8.1) crashes immediately on launch on macOS 26.5 (build 25F71). The app shows no UI and exits with code 133.
Environment
Error Output
Running the executable directly:
Crash type:
EXC_BREAKPOINT/SIGTRAPinv8::Isolate::Initialize()Full crash log excerpt (from
~/Library/Logs/DiagnosticReports/):EXC_BREAKPOINT, signalSIGTRAPTrace/BPT trap: 5, byexc handlerv8::Isolate::InitializeRoot Cause Analysis
The Electron framework is compiled against the macOS 14.5 SDK. macOS 26.5 appears to have changed how
MAP_JITmemory reservations work for V8 JIT compilation (the CodeRange region). Themmapcall for the JIT code area fails during V8 isolate initialization, causing an immediate fatal crash before any UI renders.This is not a physical memory shortage — the crash persists even with 8+ GB of free RAM.
Steps to Reproduce
Things I Already Tried
xattr -rd com.apple.quarantine)codesign -vvv→ valid, notarized)--jitlessflag — still crashes--no-sandbox --disable-gpu— still crashes--disable-features=V8VmFuture— still crashescom.apple.security.cs.allow-unsigned-executable-memorySuggested Fix
Rebuild the Electron app with a newer macOS SDK (≥ the current macOS 26 SDK) so that the Electron/V8 binary is compatible with the updated
MAP_JITmemory allocation behavior on macOS 26.5. This likely requires updating the Electron version used in the build pipeline.Crash Report
Full
.ipscrash log is available in~/Library/Logs/DiagnosticReports/— happy to attach if needed.