MicrosoftEdge / MicrosoftEdge/WebView2Feedback

WPF: webview.CoreWebView2.CookieManager.GetCookiesAsync(url) crashes without exception

Open
#3,057 3 comments 0 reactions 1 assignee View on GitHub

@peiche-ms is already working on this.

Since Dec 14, 2022.

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

Description

Our Application need the cookies from a website and reading it with
webview.CoreWebView2.CookieManager.GetCookiesAsync(url) was always working.
The last weeks more and more of our customers are experiencing an issue where the application crashes without exception.

In Debug:
Application crashes VS without any exception at this line:
webview.CoreWebView2.CookieManager.GetCookiesAsync(url)

In Release:
The installed Application writes following into the Windows Event Logs (Sorry for german)

Name der fehlerhaften Anwendung: OurApplication, Version: 3.25.3.0, Zeitstempel: 0x63972986
Name des fehlerhaften Moduls: EmbeddedBrowserWebView.dll, Version: 108.0.1462.46, Zeitstempel: 0x639196b2
Ausnahmecode: 0x4000001f
Fehleroffset: 0x000aff6d
ID des fehlerhaften Prozesses: 0x73b4
Startzeit der fehlerhaften Anwendung: 0x01d90e2bf619692f
Pfad der fehlerhaften Anwendung:PathToOurApplication
Pfad des fehlerhaften Moduls: C:\Program Files (x86)\Microsoft\EdgeWebView\Application\108.0.1462.46\EBWebView\x86\EmbeddedBrowserWebView.dll
Berichtskennung: c3efdc0e-a663-472d-960b-783103d040fb
Vollständiger Name des fehlerhaften Pakets:
Anwendungs-ID, die relativ zum fehlerhaften Paket ist:

Version
Runtime: 108.0.1462.46
Framework: WPF
OS: Win10 21H2 (Build 19044.2251)

Repro Steps
Actually do not know. This Bug did not exist until last week on my PC, since this week i cant read the cookies.
I guess a windows, edge or webview2 update causes that exception

Already tried to update webview2, edge and reinstall the webview2 runtime.

If you need more information i try to provide it.

AB#42609408

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.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.