MicrosoftEdge / MicrosoftEdge/WebView2Feedback
[Problem/Bug]: webview not initializing/rendering when UDF folder is not present
@LiangTheDev is already working on this.
Since Jan 2, 2025.
- Dominant language
- PowerShell
- Stars
- 526
- Forks
- 67
- PR merge metrics
- No merged PRs in 30d
Description
What happened?
We are using webview2 extensively. We see a new issue in one machines alone. Either the webview doesn't initialize or host object doesn't work when the UDF folder is not present and created dynamically. When the UDF folder is made to persist then the both issues are gone, rendering and host objects everything works fine.
When the issue occurs we can see that the count of the msedgewebview processes is 5 rather than 6. I succeeded to reproduce the same issue with the webview sample by adding hostobject implementation.
I observe that a msedgewebview child process is getting created again and again and are short lived. From procmon I didnt see any failures when the processes end. Sometimes the type of the process is renderer, utility, gpu-process. Majority of the short lived child processes spawned are of type utility.
One absurd thing is when I set compatibility settings for the sample webview2gettingstarted executable, then it fixes these issues. The same thing doesn't work on our application.
This is kind of blocker for us. Would really appreciate if there are any inputs.
Importance
Blocking. My app's basic functions are not working due to this issue.
Runtime Channel
Stable release (WebView2 Runtime)
Runtime Version
131.0.2903.112
SDK Version
No response
Framework
Win32
Operating System
Windows 10, Windows 11
OS Version
19045.5247
Repro steps
Opening webview by dynamically creating the UDF folder
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.
Assessment
This issue has not been assessed yet.