Hi Radzen team,
After upgrading from Radzen 10.3.2 to 10.4.1, one of my Blazor Server pages started crashing.
The same page works correctly with 10.3.2, but after upgrading to 10.4.1 the Blazor Server circuit disconnects. Other pages are working normally. The issue seems to happen only on the page where I use Popup from:
@using Radzen.Blazor.Rendering
The page contains this popup:
<Popup @ref=popup Lazy=true class="my-popup">
And it is opened from a button like this:
<RadzenButton @ref=button
Text="@(FiltereUser != null ? FiltereUser.Count() + " user Selected" : "Select user for filter")"
Click="@(args => popup.ToggleAsync(button.Element))" />
The page also has:
RadzenButton button;
Popup popup;
And closes the popup like this:
private async Task SetFilterUserList(List? arg)
{
FiltereUser = arg;
await popup.CloseAsync();
}
The issue does not happen with Radzen 10.3.2. It started after updating to 10.4.1.
Browser console output:
blazor.web.js:1 [2026-05-13T09:48:11.609Z] Information: Normalizing '_blazor' to 'http://localhost:56124/_blazor'.
browserLink:4 [Violation] Permissions policy violation: unload is not allowed in this document.
blazor.web.js:1 [2026-05-13T09:48:11.623Z] Information: WebSocket connected to ws://localhost:56124/_blazor?id=1nsFBXwrCioiJM-PlWiyKg.
blazor.web.js:1 [Violation] Permissions policy violation: unload is not allowed in this document.
blazor.web.js:1 [2026-05-13T09:48:58.331Z] Error: System.Exception: Cannot access a disposed object.
Object name: 'Session factory with id f9158e9f4b514a16aaa51fb8de500cf3'.
at BlazorEcommerce.Services.Data.Repository.NhEntityRepositoryBase`1.Search(Expression`1 filter, ExtraFilter extraFilter) in C:\BlazorEcommerce\BlazorEcommerce\BlazorEcommerce.Services\Data\Repository\NhEntityRepositoryBase.cs:line 51
at BlazorEcommerce.ServerTest.Components.Pages.PalletDetail.PalletDetailListViewPage.OnInitializedAsync() in C:\BlazorEcommerce\BlazorEcommerce\BlazorEcommerce.ServerTest\Components\Pages\PalletDetail\PalletDetailListViewPage.razor:line 603
at Microsoft.AspNetCore.Components.ComponentBase.RunInitAndSetParametersAsync()
at Microsoft.AspNetCore.Components.RenderTree.Renderer.HandleExceptionViaErrorBoundary(Exception error, ComponentState errorSourceOrNull)
blazor.web.js:1 [2026-05-13T09:48:58.332Z] Information: Connection disconnected.
blazor.web.js:1 Uncaught Error: No interop methods are registered for renderer 1
at A (blazor.web.js:1:13826)
at blazor.web.js:1:13732
at D (blazor.web.js:1:13915)
at R (blazor.web.js:1:13706)
at P.dispatchGlobalEventToAllElements (blazor.web.js:1:16308)
at P.onGlobalEvent (blazor.web.js:1:15501)
After the circuit disconnects, this message repeats many times:
Uncaught Error: No interop methods are registered for renderer 1
Important details:
This page works with:
Radzen 10.3.2
But fails with:
Radzen 10.4.1
The issue seems related to the page where I use:
<Popup @ref=popup Lazy=true>
Other pages without this popup do not show the same problem.
Question:
Was there any change in Popup, Lazy=true, or ToggleAsync(button.Element) behavior between 10.3.2 and 10.4.1?
Is there a recommended replacement or safer usage pattern for this popup in Radzen 10.4.1?
For example, should I avoid:
popup.ToggleAsync(button.Element)
or should I replace Popup with another Radzen component such as RadzenPopup, RadzenDialog, or another supported API?
Thanks.