Skip to content

[Bug]: Windows main process exits with EXCEPTION_ACCESS_VIOLATION when loading or restoring a Chrome Web Store tab #1637

Closed

Description

@wesleyfei1

OpenBot version or commit

OpenBot 0.33.0, installed Windows desktop distribution. Original app.asar SHA-256: 95248b9c50c65842cdc0a04b88867d576db59e3d5863a9654bb2c34f7347f64d.

Environment

Windows 11, build 10.0.22631, x64. Custom ACP agent: Oh My Pi 18.8.4. Not a source build. No Computer Use automation was used for this investigation.

A later local runtime-metadata query identified Electron 44.0.0, Chromium 152.0.7977.54 and V8 15.2.124.13.

What happened?

OpenBot began exiting a few seconds after launch. Diagnostic startup captured a native EXCEPTION_ACCESS_VIOLATION and exit code 5. There was no useful report in the application's saved error-report list, and the queried Windows Application events did not provide a matching crash report.

The saved embedded-browser state contained two tabs: a GitHub issue and this public Chrome Web Store listing:

https://chromewebstore.google.com/detail/chatgpt-exporter-chatgpt/ilmdofdhpnhffldihboadndccenlnfll?hl=zh-CN&pli=1

Backing up the state file and excluding the Chrome Web Store tab from startup restoration, while retaining the GitHub tab and all other application data, stopped the immediate native exit in the observations below. This isolates a trigger in this profile; it does not establish the underlying native defect, prove that the extension itself was installed, or prove that every profile visiting this URL will crash.

Observed isolation results

Launch condition Observed result
Original two tabs, diagnostic logging enabled Exit code 5 after 6.921 seconds; native access violation
Original two tabs, --js-flags=--no-concurrent-recompilation Same native failure after 6.473 seconds
Original two tabs, --js-flags=--jitless Same native failure after 8.005 seconds; also introduced WebAssembly/networking errors, so this is not a workaround
No restored tabs, otherwise original profile Survived 110 seconds; then deliberately stopped for the next isolation run
GitHub tab restored, Chrome Web Store tab omitted Survived 119 seconds; process reported responding; then deliberately stopped
Ordinary launch without diagnostic flags, Chrome Web Store tab omitted Alive and responding at 30 seconds; a separate ACP history initialization error was displayed instead of the native crash

Expected: restoring a saved browser tab should not terminate the desktop main process. A failing tab should be isolated/recoverable without losing access to the workspace.

Reproduction steps

These steps describe the affected profile and the observed startup path. A clean-profile reproduction has not been established.

  1. In the affected installed Windows build, persist the above Chrome Web Store page as an embedded-browser tab.
  2. Exit and reopen OpenBot with that saved state.
  3. For diagnostics, launch OpenBot.exe --enable-logging=stderr with ELECTRON_ENABLE_LOGGING=1 and ELECTRON_ENABLE_STACK_DUMPING=1 and capture stdout/stderr and the exit status.
  4. Observe the native access violation shortly after startup.
  5. While the app is stopped, back up openbot-browser-state-v1.json, remove only the Chrome Web Store entry from its restored tabs, and select a retained tab as active.
  6. Start OpenBot again. In the affected profile, retaining the other tab did not reproduce the immediate native exit.

No conversation database, credentials, agent configuration, or model configuration was reset. Do not use a full profile reset as a reproduction prerequisite.

Redacted diagnostics

Received fatal exception EXCEPTION_ACCESS_VIOLATION
    OpenBot!llhttp_message_needs_eof [...]
    OpenBot!v8::internal::compiler::CompilationDependencies::PrepareInstallPredictable [...]
    OpenBot!v8::Object::Wrap [...]
    OpenBot!v8::Isolate::Dispose [...]
    OpenBot!v8::internal::OptimizingCompileTaskExecutor::OptimizingCompileTaskExecutor [...]
    KERNEL32!BaseThreadInitThunk [...]
    ntdll!RtlUserThreadStart [...]

The captured native stack is included below as native-crash-redacted.txt. These are the executable's emitted symbols, not a fully symbolized crash dump; do not infer a particular JIT, HTTP, or GPU defect from the nearest symbol names alone.

A separate JavaScript error in custom ACP history recovery was uncovered after excluding the crashing restoration entry. It is documented separately rather than being presented as the cause of the native crash.

Recurrence during ordinary interaction

The same native failure later occurred when an agent opened this page during an existing chat, not only while restoring it at startup. A text-only chat probe initially produced its requested answer, but an omp unfinished-todo reminder then caused the old browser task to resume and open the page. The page's console messages were followed by the same native access violation and exit code 5. The distinct todo-continuation behavior is being reported as additional evidence on can1357/oh-my-pi#8038.

An additional diagnostic launch with --disable-gpu also exited with code 5. Removing the restoration entry alone is therefore not a durable fix: a later browser operation can recreate the tab and trigger another crash. Pausing the stale tasks prevents this particular automatic route to the trigger, but does not repair the native browser defect.

Checklist

  • Searched existing GitHub issues, including access-violation and browser-crash reports; no exact match was found.
  • Removed credentials, private paths, conversation contents, and agent/session identifiers from this draft and its public attachment.
  • This is a stability report, not a vulnerability claim.

Attachment safety

Only reviewed, redacted excerpts are included below. Profile databases, original browser-state files, raw logs, and installation backups remain private.

native-crash-redacted.txt
OpenBot 0.33.0; Windows 11 build 22631 x64; installed desktop build.
Original restored tabs: a GitHub issue and the Chrome Web Store ChatGPT Exporter listing.
Baseline: process exited after 6921 ms with exit code 5.
Received fatal exception EXCEPTION_ACCESS_VIOLATION
	OpenBot!llhttp_message_needs_eof [0x7ff69c95e9ad+23be7d]
	OpenBot!llhttp_message_needs_eof [0x7ff69c8860e2+1635b2]
	OpenBot!llhttp_message_needs_eof [0x7ff69c88a5ac+167a7c]
	OpenBot!llhttp_message_needs_eof [0x7ff69c889b80+167050]
	OpenBot!llhttp_message_needs_eof [0x7ff69c883c85+161155]
	OpenBot!v8::internal::compiler::CompilationDependencies::PrepareInstallPredictable [0x7ff69c16ab12+110c822]
	OpenBot!llhttp_message_needs_eof [0x7ff69c884e7a+16234a]
	OpenBot!v8::Object::Wrap [0x7ff698199c25+e195]
	OpenBot!v8::Object::Wrap [0x7ff698198cbe+d22e]
	OpenBot!v8::internal::compiler::CompilationDependencies::FieldTypeDependencyOffTheRecord [0x7ff69858c28f+1a39f]
	OpenBot!cppgc::internal::ExplicitManagementImpl::Resize [0x7ff69767194d+884bd]
	OpenBot!v8::Number::New [0x7ff6976d6759+26a59]
	OpenBot!v8::Value::BooleanValue [0x7ff6958cad51+3721]
	OpenBot!v8::Isolate::Dispose [0x7ff696467a33+735b3]
	OpenBot!v8::Symbol::GetIterator [0x7ff696535806+5036]
	OpenBot!v8::internal::OptimizingCompileTaskExecutor::OptimizingCompileTaskExecutor [0x7ff698a233f3+2b03]
	OpenBot!v8::internal::OptimizingCompileTaskExecutor::OptimizingCompileTaskExecutor [0x7ff698a2322d+293d]
	OpenBot!v8::internal::OptimizingCompileTaskExecutor::OptimizingCompileTaskExecutor [0x7ff698a22fd6+26e6]
	OpenBot!v8::internal::OptimizingCompileTaskExecutor::OptimizingCompileTaskExecutor [0x7ff698a220ff+180f]
	OpenBot!v8::HeapSpaceStatistics::operator= [0x7ff6989f7f08+4fec8]
	OpenBot!v8::HeapSpaceStatistics::operator= [0x7ff6989f7209+4f1c9]
	OpenBot!v8::HeapSpaceStatistics::operator= [0x7ff6989f65a7+4e567]
	OpenBot!v8::HeapSpaceStatistics::operator= [0x7ff6989f5f7d+4df3d]
	OpenBot!v8::internal::compiler::CompilationDependencies::CompilationDependencies [0x7ff698888492+274c92]
	KERNEL32!BaseThreadInitThunk [0x7ffe0428259d+1d]
	ntdll!RtlUserThreadStart [0x7ffe059eaf38+28]

Isolation: no restored tabs survived 110 seconds; GitHub-only restoration survived 119 seconds. Both diagnostic instances were manually stopped, not crashed.
No debugger-symbolized dump or fresh-profile reproduction was collected. Native root cause remains undetermined.

Activity

  1. self-assigned this
    on Oct 9, 2026
  2. added a commit that references this issue on Oct 9, 2026
    ae84d6f
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions