# Codex VS Code renderer crashes during concurrent agent streaming **URL:** \ **Category:** Codex\ **Tags:** bug\ **Created:** [August 9, 2026, 8:38pm UTC](https://community.openai.com/t/codex-vs-code-renderer-crashes-during-concurrent-agent-streaming/1389759 "2026-08-09T20:38:33Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![farhad.g1980](https://avatars.discourse-cdn.com/v4/letter/f/50afbb/32.png) [@farhad.g1980](https://community.openai.com/u/farhad.g1980)\ **Post date:** [August 9, 2026, 8:38pm UTC](https://community.openai.com/t/codex-vs-code-renderer-crashes-during-concurrent-agent-streaming/1389759/1 "2026-08-09T20:38:34Z")
I am seeing repeatable full VS Code renderer crashes while the Codex extension is streaming a long-running task with multiple concurrent/background agent threads. ## Environment - Windows 10.0.26200.8973 (x64) - VS Code 1.132.0 (`df53daabb18cd157bdb08c7f01c34df936cf12f4`) - Codex extension 26.803.41515 - Bundled Codex CLI 0.147.0-alpha.6.5 ## Crash signature Three crashes on the same day produced the same minidump signature: - `EXCEPTION_BREAKPOINT` - Crashing instruction: `int 0x3` - Crashed thread: `CrRendererMain` - Top frame: `Code.exe + 0x2350820` Local symbol analysis maps this offset to Blink’s `Document::UpdateStyleAndLayoutTreeForThisDocument()` lifecycle check. Immediately before the latest crash, the Codex log repeatedly contained: `[desktop-notifications][global-error] ResizeObserver loop completed with undelivered notifications.` In the latest session: - 308 ResizeObserver loop errors - 683 completed reasoning-summary item events - During the final ~197 seconds: 7 distinct streaming threads, 77 reasoning-summary events, and 41 ResizeObserver errors The dump was written at 23:26:47, followed by renderer/extension-host termination at 23:26:49. The extension host received termination from the renderer, so its shutdown errors appear downstream of the renderer failure. ## Configuration/workaround result I set: `model_reasoning_summary = "none"` The turn-start log confirmed: - `summary=none` - `concurrentReasoningSummariesFeatureOverrideEnabled=false` However, the extension continued receiving hundreds of empty summary events (`summary=[]`, `summaryPartCount=0`) and the renderer crashed again. This workaround did not prevent the failing UI update path in this environment. ## Reproduction 1. Open the Codex sidebar in VS Code. 2. Resume a long-running local thread. 3. Run multiple background/subagent threads concurrently. 4. Repeated ResizeObserver errors appear. 5. The VS Code renderer terminates and the window closes; the local session transcript remains recoverable after restart. ## Expected Streaming updates from concurrent Codex threads should not violate Blink layout lifecycle invariants or terminate the VS Code renderer. ## Related reports - [VS Code extension 26.707: streaming warning loop repeatedly crashes renderer with SIGILL on Linux · Issue #33042 · openai/codex · GitHub](https://github.com/openai/codex/issues/33042) - [[Linux] VS Code renderer crashes when opening Codex sidebar in 26.707.91948; rollback to 26.707.71524 fixes it · Issue #33521 · openai/codex · GitHub](https://github.com/openai/codex/issues/33521) - [Windows Desktop: concurrent reasoning summaries correlate with ResizeObserver loops and UI freezes · Issue #33996 · openai/codex · GitHub](https://github.com/openai/codex/issues/33996#issuecomment-5141351167) I can provide sanitized log excerpts or minidump metadata if maintainers need them. I am intentionally not attaching the raw dump publicly because it may contain process memory. ---
**Author:** ![EricGT](https://sea2.discourse-cdn.com/openai1/user_avatar/community.openai.com/ericgt/32/20571_2.png) [@EricGT](https://community.openai.com/u/EricGT)\ **Post date:** [August 9, 2026, 9:27pm UTC](https://community.openai.com/t/codex-vs-code-renderer-crashes-during-concurrent-agent-streaming/1389759/2 "2026-08-09T21:27:03Z")
Welcome to the forum! Thank you for your section on **Related reports** You are welcome to discuss Codex issues here. However, the official place to report and track them is the [OpenAI Codex GitHub issue tracker](https://github.com/openai/codex/issues). Remember to add a 👍 reaction on the GitHub issue to help the developers gauge the number of affected users. If none of those issues describe the same problem, open a new issue and include as much relevant detail as possible. ---
**Author:** ![OpenAI\_Support](https://sea2.discourse-cdn.com/openai1/user_avatar/community.openai.com/openai_support/32/561845_2.png) [@OpenAI\_Support](https://community.openai.com/u/OpenAI_Support)\ **Post date:** [October 11, 2026, 9:01pm UTC](https://community.openai.com/t/codex-vs-code-renderer-crashes-during-concurrent-agent-streaming/1389759/3 "2026-10-11T21:01:20Z")
Hi [farhad.g1980](https://community.openai.com/u/farhad.g1980), Thanks for the detailed analysis! I understand the crashes continued even with reasoning summaries disabled. Since some time has passed since your report, could you check whether the issue still persists? - Saif ---
**Author:** ![saifa2762](https://avatars.discourse-cdn.com/v4/letter/s/c5a1d2/32.png) [@saifa2762](https://community.openai.com/u/saifa2762)\ **Post date:** [October 15, 2026, 9:28pm UTC](https://community.openai.com/t/codex-vs-code-renderer-crashes-during-concurrent-agent-streaming/1389759/4 "2026-10-15T21:28:21Z")