Duplicated
Last Updated: 31 Aug 2020 12:08 by ADMIN
Mr Chas
Created on: 29 Aug 2020 08:21
Category: UI for Blazor
Type: Bug Report
0
Cannot process pending renders after the renderer has been disposed. Object name: 'Renderer'.

Just wondering if there has been any movement on this issue. We are seeing this in our production system application insights logs. Thanks!

System.ObjectDisposedException: at Microsoft.AspNetCore.Components.RenderTree.Renderer.ProcessPendingRender (Microsoft.AspNetCore.Components, Version=3.1.7.0, Culture=neutral, PublicKeyToken=adb9793829ddae60) at Microsoft.AspNetCore.Components.Server.Circuits.RemoteRenderer.ProcessPendingRender (Microsoft.AspNetCore.Components.Server, Version=3.1.6.0, Culture=neutral, PublicKeyToken=adb9793829ddae60) at Microsoft.AspNetCore.Components.RenderTree.Renderer.AddToRenderQueue (Microsoft.AspNetCore.Components, Version=3.1.7.0, Culture=neutral, PublicKeyToken=adb9793829ddae60) at Microsoft.AspNetCore.Components.ComponentBase.StateHasChanged (Microsoft.AspNetCore.Components, Version=3.1.7.0, Culture=neutral, PublicKeyToken=adb9793829ddae60) at Microsoft.AspNetCore.Components.Rendering.RendererSynchronizationContextDispatcher.InvokeAsync (Microsoft.AspNetCore.Components, Version=3.1.7.0, Culture=neutral, PublicKeyToken=adb9793829ddae60) at Telerik.Blazor.Components.RootComponent.TelerikFragmentContainer.Refresh (Telerik.Blazor, Version=2.16.0.0, Culture=neutral, PublicKeyToken=20b4b0547069c4f8) at Telerik.Blazor.Components.RootComponent.TelerikRootComponentFragment.Dispose (Telerik.Blazor, Version=2.16.0.0, Culture=neutral, PublicKeyToken=20b4b0547069c4f8) at Microsoft.AspNetCore.Components.Rendering.ComponentState.Dispose (Microsoft.AspNetCore.Components, Version=3.1.7.0, Culture=neutral, PublicKeyToken=adb9793829ddae60) at Microsoft.AspNetCore.Components.RenderTree.Renderer.Dispose (Microsoft.AspNetCore.Components, Version=3.1.7.0, Culture=neutral, PublicKeyToken=adb9793829ddae60)

Related:

https://feedback.telerik.com/blazor/1451036-system-objectdisposedexception-cannot-process-pending-renders-after-the-renderer-has-been-disposed-when-i-refresh-a-page-with-f5

https://feedback.telerik.com/blazor/1446870-window-throws-cannot-process-pending-renders-after-the-renderer-has-been-disposed-when-the-user-closes-the-page

Duplicated
This item is a duplicate of an already existing item. You can find the original item here:
3 comments
Mr Chas
Posted on: 31 Aug 2020 08:24
Not seeing the app break right now. Just getting a lot of log entries in app insights.
Mr Chas
Posted on: 31 Aug 2020 08:24
Not seeing the app break right now. Just getting a lot of log entries in app insights.
ADMIN
Svetoslav Dimitrov
Posted on: 31 Aug 2020 08:22

Hello Charles,

They originate from the lack of proper OnUnmounted lifecycle hook in the framework, which is logged in the ASPNET Core GitHub repository (issue). We have raised the priority of those exceptions, internally, in order to provide a workaround solution until Microsoft implement a proper method. 

Could you confirm whether they break the app?

Regards,
Svetoslav Dimitrov
Progress Telerik

Virtual Classroom, the free self-paced technical training that gets you up to speed with Telerik and Kendo UI products quickly just got a fresh new look + new and improved content including a brand new Blazor course! Check it out at https://learn.telerik.com/.