MicrosoftEdge / MicrosoftEdge/WebView2Feedback

[Problem/Bug]: Getting the error STATUS_ACCESS_VIOLATION while accessing window.chrome.webview

Open
#4,858 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
PowerShell
Stars
526
Forks
67
PR merge metrics
No merged PRs in 30d

Description

What happened?

While accessing the property window.chrome.webview I'm getting the error STATUS_ACCESS_VIOLATION.
This happens in a simple if statement like so:
if (window.chrome.webview == null)
I have an winforms app that is hosting a third party page that has that code. I don't have much info about the third party page, but a simple html test page with this code works. The third party page when opened in Edge also works.

I'm receiving the event CoreWebView2.ProcessFailed. The CoreWebView2ProcessFailedEventArgs has the following data:

ExitCode: -1073741819
FailureSourceModulePath: ""
FrameInfosForFailedProcess: null
ProcessDescription: ""
ProcessFailedKind: RenderProcessExited
Reason: Crashed

Importance

Blocking. My app's basic functions are not working due to this issue.

Runtime Channel

Stable release (WebView2 Runtime)

Runtime Version

129.0.2792.79

SDK Version

1.0.2792.45

Framework

Winforms

Operating System

Windows 10, Windows 11

OS Version

No response

Repro steps

The only way I can reproduce the problem is by using the third party page. I don't have much info about this page.

Repros in Edge Browser

No, issue does not reproduce in the corresponding Edge version

Regression

No, this never worked

Last working version (if regression)

No response

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No repository files or tests are named. Start by obtaining a reproducible copy of the third-party page, compare the failing WinForms WebView2 case with the supplied simple HTML page and Edge, and inspect the reported CoreWebView2.ProcessFailed data. Done requires a reproducible case and a confirmed cause or actionable resolution for the renderer crash.

Written by the indexing model from the issue text.

Assessment

Domain
desktop
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.