[Windows][26.908.4834.0] In-app browser renderer crashes with 0x80000003; recovery requests reject the internal crash page

Codex App version

Microsoft Store/MSIX OpenAI.Codex 26.908.4834.0; desktop / Browser Use release 26.908.40834. Bundled app-server at inspection: 0.154.0-alpha.6.2.

Platform

Windows x64, registry-reported DisplayVersion 26H1, OS build 28000.2954. Subscription tier was not collected.

What happened

On September 13, 2026 at 01:17:01 UTC, the in-app Browser Use renderer crashed while viewing a localhost development page. The main desktop process continued logging afterward. Crashpad independently recorded capture_kind=crash, ptype=renderer.

The browser lifecycle log reports reason=crashed and exitCode=-2147483645 (32-bit hexadecimal 0x80000003). This report does not infer a native faulting module or assertion from that exit code.

During recovery, the app tried to load its internal data:text/html;charset=utf-8,... error document titled “This page crashed”. Logs then recorded both Inspected target navigated or closed from the loadBrowserErrorPage path and repeated Blocked browser navigation by Browser Use URL policy errors involving that same internal error-page URL.

Sanitized evidence

2026-09-13T01:17:01.604Z Crashpad renderer sidecar last-write time
2026-09-13T01:17:01.615Z [browser-sidebar-manager] browser sidebar render process gone exitCode=-2147483645 reason=crashed url=<localhost development page>
2026-09-13T01:17:01.628Z [browser-use-iab-api] debugger render process gone exitCode=-2147483645 reason=crashed tabId=5 webContentsId=10
2026-09-13T01:17:01.628Z [browser-use-iab-api] unregistered debugger listener reason=render-process-gone webContentsDestroyed=false
2026-09-13T01:17:01.631Z [browser-use-iab-api] iab backend request failed errorMessage="Inspected target navigated or closed"
2026-09-13T01:17:01.640Z [browser-sidebar-manager] blocked browser-use navigation errorMessage="Blocked browser navigation by Browser Use URL policy: data:text/html;charset=utf-8,<internal crash-page HTML omitted>"
2026-09-13T01:17:01.815Z [browser-sidebar-manager] browser sidebar dom-ready url=data:text/html;charset=utf-8,<internal crash-page HTML omitted>
2026-09-13T01:17:20.458Z [browser-sidebar-manager] blocked browser-use navigation <same internal error-page URL>
2026-09-13T01:17:20.459Z [browser-use-iab-api] iab backend request failed <same URL policy rejection>
2026-09-13T01:18:23.826Z [browser-sidebar-manager] blocked browser-use navigation <same internal error-page URL>

Relevant sanitized recovery stack frame:

$Be.loadBrowserErrorPage
  app.asar/.vite/build/main-D8abTQQE.js:1088:53662

The later dom-ready event means this evidence does not establish that the error document never rendered. It does show that subsequent Browser Use requests encountered repeated policy failures during recovery.

Reproduction status and expected behavior

Observed once in the retained September 11–14 crash metadata. The recorded workflow was an active Browser Use session viewing a local development page. The precise action that triggered the native renderer crash has not been established, and no deterministic reproduction or native stack is available.

Expected: the guest renderer should remain stable during ordinary browsing. If a guest does crash, the application should display a recoverable error state and permit supported reload/recovery operations without repeatedly treating its own internal error page as an unsupported navigation target.

Please investigate both the renderer termination and the error-page recovery lifecycle. The URL-policy errors occur after the crash and are not claimed to cause it. Any fix should preserve policy checks on external page navigations.

Related reports and limits

#43347 covers a separate browser/main-process termination after Browser Use teardown. This event is a guest-renderer crash with continued main-process logging and is not included in the ten main-process events reported there today. #45247 describes a different native renderer signature (C000001D); there is no evidence that the signatures share a root cause.

No minidump remains locally. Crashpad metadata does not confirm automatic upload receipt. Submitted after local log review at the affected user's request; private URLs, paths, task/session IDs, prompts, and raw logs are omitted.

Start with app.asar/.vite/build/main-D8abTQQE.js:1088:53662 and the browser-sidebar-manager/browser-use-iab-api recovery logs. Trace how the renderer crash and internal data URL move through loadBrowserErrorPage and URL policy checks; done means a recoverable crash state with supported reload/recovery while external navigation policy remains enforced.