MicrosoftEdge / MicrosoftEdge/WebView2Feedback
[Problem/Bug]: POSTing large files, when inetercepting resource request crashes WebView
Nobody has claimed this yet.
- Dominant language
- PowerShell
- Stars
- 526
- Forks
- 67
- PR merge metrics
- No merged PRs in 30d
Description
What happened?
Steps to reproduce
- Attach event handler to
CoreWebView2.WebResourceRequested
In Browser:
- Select file (>1.5GB, did so far not figure out the actual limit 100MB work fine) for upload
- POST file as FormData
Expected Result
Event handler receives the large payload
Actual result
WebView crashes.
Crash Produces a Windows event log entry containing:
[24884:17392:0722/143309.519:INFO:chrome\browser\extensions\extension_garbage_collector.cc:188] Garbage collection for extensions on file thread is complete.
Importance
Important. My app's user experience is significantly compromised.
Runtime Channel
Stable release (WebView2 Runtime)
Runtime Version
1.0.3800.47
SDK Version
No response
Framework
WPF
Operating System
Windows 11
OS Version
No response
Repro steps
Steps to reproduce
- Attach event handler to
CoreWebView2.WebResourceRequested
In Browser:
- Select file (>1.5GB, did so far not figure out the actual limit 100MB work fine) for upload
- POST file as FormData
Expected Result
Event handler receives the large payload
Actual result
WebView crashes.
Crash Produces a Windows event log entry containing:
[24884:17392:0722/143309.519:INFO:chrome\browser\extensions\extension_garbage_collector.cc:188] Garbage collection for extensions on file thread is complete.
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
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the WPF reproduction using CoreWebView2.WebResourceRequested and a FormData POST containing a file larger than 1.5 GB; compare it with the corresponding Edge version, where the issue does not reproduce. Done means intercepting the large resource request without crashing the WebView and receiving the expected payload.
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
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100