Repository navigation
Description
Bug type
Client crash (Windows Hub native chat)
Summary
Windows Hub 2026.10.5-alpha.4 crashes (process terminates) almost every time a chat message is sent from the native chat, against a 2026.11.1 gateway. Three crashes plus one hang within ~10 minutes. Same fault signature each time.
Possibly related to #1779 (native chat freezing after send against a newer gateway), but this is a hard crash with a stowed exception in CoreMessagingXP.dll, not just a freeze, and on the alpha build.
Environment
- Windows Hub:
OpenClawFoundation.OpenClaw_2026.10.502.0_x64(product version2026.10.5-alpha.4+Sha.f81edef9a06222e4eea5a93dd21ecfb7e3002c10), MSIX install - Windows 11 23H2, build 10.0.22631.6199, x64
- Gateway: OpenClaw 2026.11.1 (4ffdd20) on macOS,
gateway.bind: lan, token auth, plainws://over LAN (no SSH tunnel) - Hub connected as operator only. Node mode is off; the PC's node is a separate
openclaw node2026.11.1 Scheduled Task and is unaffected.
Steps to reproduce
- Connect Hub to a 2026.11.1 gateway over LAN with token auth.
- Open a session in native chat and send a message.
- Hub crashes shortly after send (or hangs, then WER reports
MoAppHang).
Crash details (Application event log)
Event 1000:
Faulting application name: OpenClaw.Tray.WinUI.exe, version: 2026.10.5.0, time stamp: 0x6ac20000
Faulting module name: CoreMessagingXP.dll, version: 10.0.27200.1054, time stamp: 0x1cff1018
Exception code: 0xc000027b
Fault offset: 0x0000000000097976
Faulting module path: ...\OpenClawFoundation.OpenClaw_2026.10.502.0_x64__rfcbke2p71se2\CoreMessagingXP.dll
Event 1001 (WER), twice with the same bucket:
Event Name: MoAppCrash
Fault bucket 1801632342227796092, type 5
P1: OpenClawFoundation.OpenClaw_2026.10.502.0_x64__rfcbke2p71se2
P3: 2026.10.5.0
P5: combase.dll P6: 10.0.22621.6133 P8: 88000fa8 P9: 0000000000042ca7
Plus one MoAppHang for the same package.
0xc000027b is a stowed (WinRT) exception, so the real exception is likely an unhandled error on the UI thread during the send/reply render path. A WER minidump exists locally and I can attach it if that helps.
Workaround
Browser Control UI against the same gateway works fine.
Metadata
Metadata
Assignees
Labels
Type
Fields
Priority
Projects
- StatusShow more project fieldsBacklog
Activity
clawsweeper commentedon Nov 7, 2026
Codex review: this still needs some work.
Summary
Keep open: this issue documents repeated crashes in an official MSIX build, and current main does not demonstrably resolve its specific chat-send failure.
Reproducibility: The report supplies specific build identities, connection settings and repeated crash records, but no current-main reproduction or underlying exception stack is available; WinApp CLI is absent, and this read-only review ran no builds or tests.
Next step
Inspect sanitized crash diagnostics or a privately shared dump, verify operator-only LAN sending on a current packaged build, and establish a failing native regression before selecting a repair with visible recovery.
Review details
Best possible solution:
Repair the diagnosed native failure and provide a visible recovery or Control UI launcher when chat cannot continue.
Do we have a high-confidence way to reproduce the issue?
The report supplies specific build identities, connection settings and repeated crash records, but no current-main reproduction or underlying exception stack is available; WinApp CLI is absent, and this read-only review ran no builds or tests.
Is this the best way to solve the issue?
Obtain the actual native exception before choosing a repair, because current source spans immediate transcript publication, Gateway dispatch and native layout, while existing catches and related mitigations do not identify this failure.
AGENTS.md: found and applied where relevant.
Remaining risk / open question:
Codex review notes: model internal, reasoning medium; reviewed against 91070a21147a.
Label changes
Label changes:
No label changes.
Label justifications:
P0: The reported basic native chat workflow repeatedly terminates or hangs the official client, with no demonstrated in-product recovery.impact:crash-loop: The reporter supplies repeated process-crash records and a whole-app hang during chat sending.impact:ux-release-blocker: The affected community user cannot continue native chat without an external browser workaround or diagnostic support.Evidence reviewed
What I checked:
src/OpenClaw.Tray.WinUI/Chat/OpenClawChatDataProvider.cs:443, 91070a21147a)tests/OpenClaw.Tray.Tests/OpenClawChatDataProviderTests.cs:4904, 91070a21147a)src/OpenClaw.Tray.WinUI/Chat/ReactorItemsViewScrollController.cs:1181, 91070a21147a)src/OpenClaw.Tray.WinUI/App.xaml.cs:418, 91070a21147a)How this review workflow works
@clawsweeper re-reviewcomments, exact-item GitHub events, scheduled/background review runs, or manual workflow dispatch.@clawsweeper re-reviewor@clawsweeper re-runon an open PR or issue to request a fresh review only.@clawsweeper reviewto request a fresh review only.@clawsweeper explainto ask for more context, or@clawsweeper stopto stop active automation.Reviewed November 21, 2026, 11:22 PM ET / November 22, 2026, 04:22 UTC.
github-actions commentedon Nov 22, 2026
This issue has been automatically marked as stale due to inactivity.
Please add updated OpenClaw Windows details or it will be closed.