An unhandled Objective-C exception #8668
Description
Pre-submit Checks
- I have searched Warp bugs and there are no duplicates
- I have searched Warp known issues page and my issue is not there
- I have an issue with AI and have included the debugging ID (Optional, but helps expedite the AI quality fix). Debugging ID instructions
- I have technical issue and have included the logs (optional, but helps expedite the bug fix). Log instructions
Describe the bug
An unhandled Objective-C exception (objc_exception_rethrow) in the NSApplication run loop that Warp's Rust code fails to catch, leading to std::terminate()
Warnings in logs that may be related:
- Expected to have session for session ID ... but doesn't exist (repeated)
- Received 'end_in_band_command_output' while not expecting to read in-band command
output - failed to get git_branches_for_command_corrections
Warp Crash Report Summary
**App:** Warp (dev.warp.Warp-Stable)
**Version:** 0.2026.02.10.11.37.01
**OS:** macOS 26.1 (25B78)
**Hardware:** MacBookPro16,1 / X86-64
**Launch:** 2026-02-12 17:25:18.9779 -0500
**Crash:** 2026-02-12 17:47:37.0176 -0500
**Incident ID:** 5A6A0D82-D777-4986-AA4C-B962F380D625
### Exception
- Type: EXC_CRASH (SIGABRT)
- Termination: Abort trap: 6
- ASI: {'libsystem_c.dylib': ['abort() called']}
### Faulting Thread (Thread 0 — main)
| # | Symbol | Image |
|---|--------|-------|
| 0 | __pthread_kill | libsystem_kernel.dylib +30766 |
| 1 | pthread_kill | libsystem_pthread.dylib +23386 |
| 2 | abort | libsystem_c.dylib +529318 |
| 3 | __abort_message | libc++abi.dylib +66238 |
| 4 | std::__terminate(void (*)()) | libc++abi.dylib +63321 |
| 5 | std::terminate() | libc++abi.dylib +63216 |
| 6 | objc_exception_rethrow | libobjc.A.dylib +201166 |
| 7 | -[NSApplication run] | AppKit +101707 |
| 8 | _RNvCs5oVP7oag9sS_4warp12run_internal | stable +60092363 |
| 9 | _RNvCs5oVP7oag9sS_4warp3run | stable +60135132 |
| 10 | _RINvNtNtCs15291XS9X6S_3std3sys9backtrace28___rust_begin_short_backtrac
eFEINtNtCs6B6lzvVVHQI_4core6result6ResultuNtCsf1Ou2fQ1zqn_6anyhow5ErrorEB19_EC
shuzXiLg4PZC_6stable | stable +23715398 |
| 11 | _RNCINvNtCs15291XS9X6S_3std2rt10lang_startINtNtCs6B6lzvVVHQI_4core6resu
lt6ResultuNtCsf1Ou2fQ1zqn_6anyhow5ErrorEE0CshuzXiLg4PZC_6stable | stable
+23715425 |
| 12 | std::rt::lang_start_internal::hba06c43da98f3f80 | stable +23764773 |
| 13 | main | stable +23716300 |
| 14 | start | dyld +26497 |
### Frequency
- 6 crashes in 2 days (5 on 2026-02-12)
- All crashes have identical stack traces
- Crash intervals decreasing: 4h → 3.8h → 12h → 14min → 22min
- Started after update from 0.2026.02.04 to 0.2026.02.10
To reproduce
Simply submitting in between two seperate tab terminals
Expected behavior
No response
Screenshots, videos, and logs
No response
Operating system (OS)
macOS
Operating system and version
26.1.0
Shell Version
No response
Current Warp version
v0.2026.02.10.11.37.stable_01
Regression
No, this bug or issue has existed throughout my experience using Warp
Recent working Warp date
No response
Additional context
No response
Does this block you from using Warp daily?
Yes, this issue prevents me from using Warp daily.
Is this an issue only in Warp?
Yes, I confirmed that this only happens in Warp, not other terminals.
Warp Internal (ignore): linear-label:b9d78064-c89e-4973-b153-5178a31ee54e
None