Skip to content

Commit

Permalink
Edits.
Browse files Browse the repository at this point in the history
  • Loading branch information
davidbritch committed Nov 13, 2024
1 parent 7c08cee commit 75e419f
Show file tree
Hide file tree
Showing 2 changed files with 3 additions and 3 deletions.
4 changes: 2 additions & 2 deletions docs/user-interface/controls/blazorwebview.md
Original file line number Diff line number Diff line change
Expand Up @@ -218,9 +218,9 @@ To play inline video in a Blazor hybrid app on iOS, in a <xref:Microsoft.AspNetC

::: moniker range=">=net-maui-9.0"

## Fix disposal deadlocks on Android
## Disposal deadlocks on Android

By default, <xref:Microsoft.AspNetCore.Components.WebView.Maui.BlazorWebView> fires and forgets the async disposal of the underlying `WebViewManager`. This reduces the number of disposal deadlocks that can occur on Android, resulting in less application hangs occurring.
By default, <xref:Microsoft.AspNetCore.Components.WebView.Maui.BlazorWebView> fires and forgets the async disposal of the underlying `WebViewManager`. This reduces the potential for disposal deadlocks to occur on Android.

> [!WARNING]
> This fire-and-forget default behavior means that disposal can return before all objects are disposed, which can cause behavioral changes in your app. The items that are disposed are partially Blazor's own internal types, but also app-defined types such as scoped services used within the <xref:Microsoft.AspNetCore.Components.WebView.Maui.BlazorWebView> portion of your app.
Expand Down
2 changes: 1 addition & 1 deletion docs/whats-new/dotnet-9.md
Original file line number Diff line number Diff line change
Expand Up @@ -153,7 +153,7 @@ To opt into using the `0.0.0.1` address, add the following code to the `CreateMa
AppContext.SetSwitch("BlazorWebView.AppHostAddressAlways0000", true);
```

<xref:Microsoft.AspNetCore.Components.WebView.Maui.BlazorWebView> now fires and forgets the async disposal of the underlying `WebViewManager` by default. This reduces the number of disposal deadlocks that can occur on Android, resulting in less application hangs occurring.
By default, <xref:Microsoft.AspNetCore.Components.WebView.Maui.BlazorWebView> now fires and forgets the async disposal of the underlying `WebViewManager`. This reduces the potential for disposal deadlocks to occur on Android.

> [!WARNING]
> This fire-and-forget default behavior means that disposal can return before all objects are disposed, which can cause behavioral changes in your app. The items that are disposed are partially Blazor's own internal types, but also app-defined types such as scoped services used within the <xref:Microsoft.AspNetCore.Components.WebView.Maui.BlazorWebView> portion of your app.
Expand Down

0 comments on commit 75e419f

Please sign in to comment.