Why WebViewManager can still send messages to WebView2 after BlazorWebView Unloaded event.

[yurastanchuk]

Because of this issue , I have to dispose webview processes manually. I do it as following after window close event:

But still even with delay of 10 seconds after BlazorWebView Unloaded event, I still sometimes get error 'Cannot access a disposed object'. Why this can happen and how to properly close webview process to avoid this error?

Full error: error.txt

[yurastanchuk]

upd: the message received after BlazorWebView Unloaded event is : "__bwv:["OnRenderCompleted",6,null]"

[MackinnonBuck]

@yurastanchuk, it looks like the problem is that the code in your screenshot is directly disposing the underlying WebView2Control rather than disposing the BlazorWebView itself. This will result in other resources managed by BlazorWebView to continue attempting to access the underlying WebView2Control without knowing it has been disposed. Could you please try invoking webView.DisposeAsync() instead? Thanks!

[yurastanchuk]

The same error after i have changed the code to :

[MackinnonBuck]

@yurastanchuk could you please provide a minimal repro project demonstrating the issue, hosted as a public GitHub repository? This will help us investigate the issue further. Thanks!