[BUG] Regression in 2.1.227: interactive sessions crash repeatedly on Windows 11 (2.1.226 on same machine unaffected)

Environment

• OS: Windows 11 Home (10.0.22621), native (non-WSL) install
• Install: native build via claude install (npm registry)
• TUI: "tui": "fullscreen" in user settings
• Terminal: Windows terminal environment, project paths contain Japanese (UTF-8) characters

Summary

Starting exactly with 2.1.227 (released 2026-08-10), interactive sessions began crashing / dying unexpectedly, multiple times per day — e.g. twice within a single working session today. The problem persists on 2.1.228.

The strongest evidence this is a 227 regression: a concurrently running session on the same machine still on 2.1.226 has never crashed, while 2.1.227/2.1.228 sessions on the same machine, same projects, crash repeatedly. Nothing else about the environment changed between 2026-08-08 (226, stable) and 2026-08-10 (227, crashes began).

What I suspect

• 2.1.227's changelog includes an event-loop performance change ("fewer event-loop stalls on file-not-found suggestions and at-mention size checks"), which is the only entry touching core loop behavior in that release.
• 2.1.228's changelog leads with "Fixed interactive sessions that could stop redrawing entirely, while the process kept running, after a rare internal layout error" — suggesting related rendering/session-stability regressions were already known around 227. 228 did not fix the crashes we see.

Workaround

Pinned back to 2.1.226 (claude install 2.1.226) and disabled auto-update (DISABLE_AUTOUPDATER=1).

Notes

• No crash dump / stack trace found under ~/.claude. If there is a crash-log location on Windows I should collect from, happy to provide more data.
• Happy to test candidate builds.