Repository navigation
Description
Operating system
Windows
Orca version
1.4.109.0
Details
Summary
Orca repeatedly freezes on Windows when opening or activating a workspace/session. After the freeze, Windows reports AppHangB1 for Orca.exe, and orca status --json reports that the app is no longer running with the runtime stuck in stale_bootstrap.
This still reproduces after a full reboot, after removing a previously heavy workspace (open-design), and after reopening the session. It does not look like a renderer heap or system memory exhaustion issue: the latest trace breadcrumbs show the renderer heap around 78 MB, and the machine still had significant free physical memory.
This appears related to the existing Windows terminal freeze reports:
- [Bug]: Whole window freezes, no input in any pane; frozen and other sessions close on click (Windows) #5787
- [Bug]: Starting Grok in a local worktree terminal freezes the Orca window. #4436
- [Bug]: Terminal freezes for seconds when pasting long text on Windows #5365
- [Bug]: Scrolling in agent/terminal panes causes duplicated/garbled text and panel content overlap (Windows + WSL) #5345
Environment
- Orca executable version:
1.4.109.0 - Previously reproduced on Orca
1.4.103.0 - Daemon pid file currently still reports
appVersion: "1.4.103"even though the executable is1.4.109.0 - OS: Windows 11 Pro,
10.0.26200, x64 - WSL: Ubuntu workspaces accessed via UNC paths like
\\wsl.localhost\Ubuntu\home\<redacted>\workspace\... - GPU: AMD Radeon(TM) Graphics
- Driver version:
31.0.12042.4 - Driver date:
2022-10-19
- Driver version:
- Virtual display adapters present:
- ToDesk Virtual Display Adapter, driver
16.44.2.509
- ToDesk Virtual Display Adapter, driver
- Physical memory: 32 GB
Symptoms
- Opening or activating a workspace/session can freeze the entire Orca window.
- After the freeze, the Orca GUI/runtime is unavailable from the CLI.
- The daemon process may remain alive, but the app/runtime is gone or unreachable.
- This can happen repeatedly in the same day, including after reboot.
- The issue is not resolved by removing a heavy workspace/repo from Orca.
Latest observed failure
After the latest freeze:
{
"id": "local-status",
"ok": true,
"result": {
"app": {
"running": false,
"pid": null
},
"runtime": {
"state": "stale_bootstrap",
"reachable": false,
"runtimeId": null
},
"graph": {
"state": "not_running"
}
},
"_meta": {
"runtimeId": "none"
}
}Only the daemon process remained:
Orca.exe pid 23896
Responding: true
ProductVersion: 1.4.109.0
Private memory: ~60 MB
The daemon pid file:
{
"pid": 23896,
"startedAtMs": null,
"entryPath": "C:\\Users\\<redacted>\\AppData\\Local\\Programs\\orca\\resources\\app.asar.unpacked\\out\\main\\daemon-entry.js",
"appVersion": "1.4.103"
}Windows Event Log
Repeated Application Hang / AppHangB1 events were recorded:
2026-06-30 16:18:35 Application Hang
Program Orca.exe version 1.4.109.0 stopped interacting with Windows and was closed.
2026-06-30 16:18:35 Windows Error Reporting
Event Name: AppHangB1
P1: Orca.exe
P2: 1.4.109.0
P3: 6a16071b
P4: 76a1
P5: 134217728
Other repeated Orca hangs from the same day:
2026-06-30 15:01:13 Orca.exe 1.4.109.0 AppHangB1
2026-06-30 14:57:55 Orca.exe 1.4.103.0 AppHangB1
2026-06-30 14:52:15 Orca.exe 1.4.103.0 AppHangB1
2026-06-30 14:47:53 Orca.exe 1.4.103.0 AppHangB1
2026-06-30 14:28:50 Orca.exe 1.4.103.0 AppHangB1
There are also Windows LiveKernelEvent / BlueScreen reports on the machine, including watchdog codes 117 and 141. I am not sure whether those are causal or a separate GPU/display-driver instability that makes the Electron/WebGL/terminal path more fragile.
Orca trace observations
From C:\Users\<redacted>\AppData\Roaming\Orca\logs\main.trace.ndjson:
- Renderer memory breadcrumbs stayed low before the hang:
usedHeapMB: around78totalHeapMB: around87heapLimitMB:3586browserWebviews:0
- The trace shows recurring WSL git scans:
git.exec remotegit.exec worktree- working directories under
\\wsl.localhost\Ubuntu\home\<redacted>\workspace\...
- A
sidebar_worktree_activatebreadcrumb appeared shortly before one of the freeze periods. - Latest trace breadcrumbs stopped around
2026-06-30 16:17:23, and Windows recorded theAppHangB1at2026-06-30 16:18:35.
Example trace timeline near the latest hang:
2026-06-30 15:56:21 sidebar_worktree_activate
2026-06-30 15:58:13 git.exec remote
2026-06-30 16:00:13 git.exec remote
2026-06-30 16:02:13 git.exec remote
2026-06-30 16:04:13 git.exec remote
2026-06-30 16:06:13 git.exec remote
2026-06-30 16:08:13 git.exec remote
2026-06-30 16:10:13 git.exec remote
2026-06-30 16:12:13 git.exec remote
2026-06-30 16:14:13 git.exec remote
2026-06-30 16:16:13 git.exec remote
2026-06-30 16:17:23 renderer_memory
2026-06-30 16:18:35 Windows AppHangB1 for Orca.exe 1.4.109.0
Expected behavior
Opening or activating a terminal/workspace session should not freeze the whole Orca window, and the runtime should remain reachable.
Actual behavior
The Orca window freezes or is closed by Windows as non-responsive. After that, orca status --json reports:
app.running: falseruntime.state: stale_bootstrapruntime.reachable: falsegraph.state: not_running
Notes
I can provide a redacted main.trace.ndjson and exported Windows Event Viewer entries if helpful.
Activity
niuhuoshan commentedon Jul 1, 2026
Some registered workspaces are plain folders without .git, but Orca still restores/manages them as workspaces with attached PTYs. This may interact badly with WSL UNC paths.
OrcaWin commentedon Jul 17, 2026
Agent reproduction package (Windows orchestration 2026-07-16)
Host context: Windows 11 / Orca 1.4.143.0 / repo path used:
docs/bug-reproductions/Labels applied: see issue labels (
has_reproorcannot_repro).Security: Do not run user-uploaded binaries from issue attachments. Recreate fixtures from the steps/scripts below.
Issue 6874 — Windows AppHangB1 when opening/activating terminal session
Status:
cannot_repro(forced hang on 1.4.143 this session)Host: Windows 11 10.0.26200 (25H2), Orca
1.4.143.0Label:
cannot_reproURL: #6874
Summary
Reporter: opening/activating a workspace/session freezes Orca; Windows records
AppHangB1forOrca.exe; afterwardorca status --jsonshowsapp.running: falseandruntime.state: stale_bootstrap. Related historical freezes: #5787, #4436, #5365, #5345.Attempt on this host (2026-07-16)
Environment
Orca.exe/orcachildren; main UI pid 13120, all Responding=true throughoutstate=ready,reachable=truebefore and afterorca terminal list: ~39 handles during testsActivation stress
Sequentially activated worktrees via
orca worktree show+orca terminal create --focusfor:C:/Users/neil/orca/orcaC:/Users/neil/orca/workspaces/orca/repoC:/Users/neil/orca/workspaces/orca/7640C:/Users/neil/orca/workspaces/orca/firewall-mobileC:/Users/neil/orca/workspaces/orca/pr-8955-addNote:
terminal createoften timed out waiting for terminal handle under load, but the app/runtime stayed reachable and Responding.Evidence:
docs/bug-reproductions/evidence/6874-activate-attempt-*.jsondocs/bug-reproductions/evidence/6874-status-before-*.json/6874-status-after-*.jsondocs/bug-reproductions/evidence/6874-processes-*.txtdocs/bug-reproductions/evidence/6874-memory-*.json(orca diagnostics memory)Event Viewer / WER
Recent Application log includes AppHangTransient for:
(Historical, not produced during this 1.4.143 activation pass.)
Files:
evidence/6874-wer-recent.txtevidence/6874-apphang-recent.txt(may be empty if no Application Hang provider hits matched)No new
AppHangB1/stale_bootstrapobserved on 1.4.143 during this attempt.Expected vs actual (this attempt)
Notes
#5787comments increateMainWindow.ts.Repro recipe if hang returns
orca status --json→ capturestale_bootstrap.Orca.exe.orca diagnostics memory --jsonif still reachable.How another agent should use this
%LOCALAPPDATA%\Programs\orca).--json, screenshots, logs) under a local folder; optionally comment results back here.cannot_repro/ needs_setup, satisfy the listed prerequisites first, then re-attempt and flip labels: removecannot_repro, addhas_reprowhen conclusive.nwparker commentedon Nov 17, 2026
Thanks for reporting this! This looks like it comes from Orca's older WSL integration, which reaches into the distro from Windows through
\\wsl.localhostpaths andwsl.exe. We've since shipped a new WSL bridge, WSL hosts, where Orca's server runs inside the distro itself, so this part of the old path isn't involved.Could you give it a try?
If it still happens there, please let us know here with your Orca version. That helps us a lot.