Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
zprettytext opened this issue May 9, 2024 · 4 comments
Open

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

zprettytext opened this issue May 9, 2024 · 4 comments
Assignees
Labels
bug Something isn't working tracked We are tracking this work internally.

Comments

@zprettytext
Copy link

zprettytext commented May 9, 2024

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

@zprettytext zprettytext added the bug Something isn't working label May 9, 2024
@lflores-ms
Copy link
Contributor

Hi @zprettytext,

It's hard to tell what happened here from just the stack. It could be the system ran out of memory or something in WebView library. How often does this happen for your app? Are you able to reproduce the issue or identified any particular scenario where this happens? Do you use WebResourceRequested events or send large data through WebView? Can you share a dump?

@zprettytext
Copy link
Author

@lflores-ms We found that starting from WebView2 version 123.0.2320.97, the probability of Out Of Memory in WebView2 has become significantly higher. At present, the company has collected about 5 related crashes. We suspect that the recent changes in WebView2 have introduced a certain BUG for the following reasons:

  1. The problems are all caused by the 64-bit version. According to regulations, there should not be insufficient memory.
  2. We have not received a similar crash dump before.
    Today we found another crash, the dump is as follows:
    image

@yildirimcagri-msft yildirimcagri-msft added the tracked We are tracking this work internally. label May 17, 2024
@yildirimcagri-msft
Copy link
Member

yildirimcagri-msft commented May 17, 2024

It seems you use WebResourceRequested event here to set some response to network requests in WebView. What is the nature of this response, can they be large, are they repeatedly set? Do you see app memory usage gradually increase over usage or whenever the WebResourceRequested is handled in this manner?

@ztextplus
Copy link

@yildirimcagri-msft Thank you very much for your reminder. We will carefully confirm the code related to the WebResourceRequested event.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working tracked We are tracking this work internally.
Projects
None yet
Development

No branches or pull requests

4 participants