-
Notifications
You must be signed in to change notification settings - Fork 51
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
Comments
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 |
@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: |
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? |
@yildirimcagri-msft Thank you very much for your reminder. We will carefully confirm the code related to the WebResourceRequested event. |
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:
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
The text was updated successfully, but these errors were encountered: