MicrosoftEdge / MicrosoftEdge/WebView2Feedback

[Problem/Bug]: No memory causing WebView2 to crash

Open
#4,548 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

What happened?

In our 64-bit Native Client, during normal use, a WebView2 error is encountered causing Native Client to crash.
The call stack is as follows:
image

Importance

Important. My app's user experience is significantly compromised.

Runtime Channel

Stable release (WebView2 Runtime)

Runtime Version

123.0.2320.97

SDK Version

1.0221

Framework

Win32

Operating System

Windows 11

OS Version

No response

Repro steps

During normal use, a WebView2 error is encountered causing Native Client to crash.

Repros in Edge Browser

No, issue does not reproduce in the corresponding Edge version

Regression

Don't know

Last working version (if regression)

No response

AB#51012422

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

Start with the attached call stack and the reported WebView2 Runtime 123.0.2320.97 and SDK 1.0.221 details, then investigate the crash during normal use in the 64-bit Win32 Native Client on Windows 11. Done means identifying a reproducible memory-related failure and documenting or validating a fix; the issue currently provides no source files, tests, or reliable reproduction steps.

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
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.