Preflight Checklist

• I have read the Contributing Guidelines for this project.
• I agree to follow the Code of Conduct that this project adheres to.
• I have searched the issue tracker for a bug report that matches the one I want to file, without success.

Electron Version

41.1.1

What operating system(s) are you using?

macOS

Operating System Version

Tahoe 26.3

What arch are you using?

x64

Last Known Working Electron version

No response

Does the issue also appear in Chromium / Google Chrome?

Yes

Expected Behavior

App launches successfully in MAS / TestFlight sandbox on ARM64, as it does when distributed as a notarised DMG.

Actual Behavior

App crashes instantly on launch with EXC_BREAKPOINT (SIGTRAP) on Thread 22 (ThreadPoolSingleThreadForegroundBlocking0). Symbolicated stack terminates at v8::internal::ThreadIsolation::UnregisterWasmAllocation. Crash occurs only under MAS/TestFlight sandbox entitlements on ARM64. The same build runs correctly as a notarised DMG and on Intel.

Testcase Gist URL

No response

Additional Information

This crash is confirmed and tracked upstream in Chromium issue 499332110 (P2/S2, assigned to vahl@chromium.org, "Unconfirmed" label removed 2026-04-06): https://issues.chromium.org/issues/499332110

Root cause: ThreadIsolation::UnregisterWasmAllocation calls mprotect() on MAP_JIT-allocated pages. macOS 26 App Sandbox tightens enforcement — MAP_JIT pages require pthread_jit_write_protect_np() for permission changes. Apple DTS (Quinn "The Eskimo!") has confirmed this is a V8 API conformance problem, not an Apple bug. Reference: "Porting just-in-time compilers to Apple Silicon" (developer.apple.com).

Same progression as macOS 11.2 / nodejs/node#37276. This crash currently blocks MAS submission for sandboxed Electron apps on macOS 26 ARM64.

Request: please subscribe to Chromium 499332110 and ensure the V8 fix lands in Electron's next V8 upgrade.