Edge backend leaks processes
See original GitHub issueWhen running a WebView with the Edge backend, two “Desktop App Web Viewer” processes are started. If the WebView window is closed (clicking the “x” or alt+f4), these processes are terminated. However, if WebView::terminate()
is called instead, these processes are never ended and will outlive the main process.
I messed around a bit with the C++ implementation of the Edge backend, and I could only get one of the processes to close (via m_process.Terminate()
).
Issue Analytics
- State:
- Created 4 years ago
- Comments:7 (4 by maintainers)
Top Results From Across the Web
Spell-Checking in Google Chrome, Microsoft Edge Browsers ...
Spell-checking features present in both the Google Chrome and Microsoft Edge browsers are leaking sensitive user information — including ...
Read more >Inspect network activity - Microsoft Edge Development
Use the Network tool to make sure the resources your webpage needs to run are downloaded as expected and that the requests to...
Read more >Debug memory leaks with the Microsoft Edge Detached ...
Memory leaks occur when the JavaScript code of an application retains more and more objects in memory that it doesn't need any longer ......
Read more >Memory leaks: the forgotten side of web performance
I've researched and learned enough about client-side memory leaks to know that most web developers aren't worrying about them too much.
Read more >Child processes leak if the process is killed · Issue #146 - GitHub
I'm submitting a... Bug report (I searched for similar issues and did not find one) Current behavior Child processes leak if the process...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
More information: windows-toolkit/Microsoft.Toolkit.Win32#146
It’s possible that this issue will eventually be resolved in Windows itself.
For Ctrl+c we will probably have to catch Windows equivalent of SIGINT so we can do graceful shutdown. Not sure if some signal can be caught for “End Task”, will need to investigate.