2023-03-14, 20:57:50
Hi,
I don't think you can change the name of the running webview2 process.
You are right, like with the browser itself, there are many processes, each for a different purpose.
One thing you could explore is to see if setting a chrome flag helps, you can set these via the AdditionalBrowserArguments property.
There are many options, more than I can list here. See the links at the forementioned property, in particular the site that lists most flags: https://peter.sh/experiments/chromium-co...-switches/
One flag there might help: --single-process
However.. I don't think you should do that and I do not think it is needed either.
Have a look at the WebView2 process model here: https://github.com/MicrosoftDocs/edge-de...s-model.md
As you can see there is only 1 Browser Process, the rest are helpers. Closing the Browser Process should notmally close the helpers as it is their parent process.
The confusion is that they all share the same name when you look at them from task manager.
Note that if a browser process fails that it normally triggers the OnProcessFailed event, which is also available from within AntView.
The following github discussion for a WPF implementation might also help understanding how things work.
https://github.com/MicrosoftEdge/WebView...issues/799
Hope this helps,
--
Wil
I don't think you can change the name of the running webview2 process.
You are right, like with the browser itself, there are many processes, each for a different purpose.
One thing you could explore is to see if setting a chrome flag helps, you can set these via the AdditionalBrowserArguments property.
There are many options, more than I can list here. See the links at the forementioned property, in particular the site that lists most flags: https://peter.sh/experiments/chromium-co...-switches/
One flag there might help: --single-process
However.. I don't think you should do that and I do not think it is needed either.
Have a look at the WebView2 process model here: https://github.com/MicrosoftDocs/edge-de...s-model.md
As you can see there is only 1 Browser Process, the rest are helpers. Closing the Browser Process should notmally close the helpers as it is their parent process.
The confusion is that they all share the same name when you look at them from task manager.
Note that if a browser process fails that it normally triggers the OnProcessFailed event, which is also available from within AntView.
The following github discussion for a WPF implementation might also help understanding how things work.
https://github.com/MicrosoftEdge/WebView...issues/799
Hope this helps,
--
Wil