System.ObjectDisposedException: Cannot process pending renders after the renderer has been disposed. when i refresh a page with F5

Progress® Telerik® UI for Blazor Feedback Portal

Create an account Log In

Back to Feed

Request a Feature Report a Bug

Completed

Last Updated: 03 Feb 2020 11:23 by ADMIN

Bostjan

Created on: 27 Jan 2020 22:39

Category: Window

Type: Bug Report

System.ObjectDisposedException: Cannot process pending renders after the renderer has been disposed. when i refresh a page with F5

Whenever i refresh a page with F5 i get the following error:

System.ObjectDisposedException: Cannot process pending renders after the renderer has been disposed.
Object name: 'Renderer'.
at Microsoft.AspNetCore.Components.RenderTree.Renderer.ProcessPendingRender()
at Microsoft.AspNetCore.Components.RenderTree.Renderer.AddToRenderQueue(Int32 componentId, RenderFragment renderFragment)
at Microsoft.AspNetCore.Components.ComponentBase.StateHasChanged()
at Microsoft.AspNetCore.Components.Rendering.RendererSynchronizationContextDispatcher.InvokeAsync(Action workItem)
at Microsoft.AspNetCore.Components.ComponentBase.InvokeAsync(Action workItem)
at Telerik.Blazor.Components.TelerikWindow.Refresh()
at Telerik.Blazor.Components.TelerikWindow.Dispose()
at System.Threading.Tasks.Task.<>c.<ThrowAsync>b__139_0(Object state)
at Microsoft.AspNetCore.Components.Rendering.RendererSynchronizationContext.ExecuteSynchronously(TaskCompletionSource`1 completion, SendOrPostCallback d, Object state)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
--- End of stack trace from previous location where exception was thrown ---
at Microsoft.AspNetCore.Components.Rendering.RendererSynchronizationContext.ExecuteBackground(WorkItem item)

Application is working normally after an error. Am i doing something wrong?

5 comments

Freenzy

Posted on: 02 Feb 2020 17:12

I think verison 2.7.0 resolved this one. I was unable to reproduce the same error.

ADMIN

Marin Bratanov

Posted on: 30 Jan 2020 14:45

Hello Bostjan,

The 2.7.0 release is out and you could give it a shot. I'd appreciate any feedback you can provide.

Regards,
Marin Bratanov
Progress Telerik

UI for Blazor

Bostjan

Posted on: 29 Jan 2020 05:07

Ok. I'll wait for 2.7.0. Thank you!

ADMIN

Marin Bratanov

Posted on: 28 Jan 2020 08:45

Hi Bostjan,

Could you check if this also causes the problem: https://feedback.telerik.com/blazor/1445426-telerik-window-is-causing-following-error-the-current-thread-is-not-associated-with-the-dispatcher? Does the issue manifest when this is not in the default (prerendered) document? At this point it looks like it is the same issue (judging by the stack trace) and it stems from a limitation in the framework related to the Dispose event and lack of a proper hook to dispose stuff when components unload.

We will have a fix for a similar problem in 2.7.0, and we have not been able to reproduce this one (we had one more report for it), so I would suggest waiting a little for the 2.7.0 release and if it does not fix the problem, please post here a sample that reproduces this error so we can investigate it.

Regards,
Marin Bratanov
Progress Telerik

UI for Blazor

Bostjan

Posted on: 27 Jan 2020 22:46

I figured out that the error occured only when i use TelerikGrid component.