You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
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
The text was updated successfully, but these errors were encountered: