Welcome to the Blazor feedback portal. We’re happy you’re here! If you have feedback on how to improve the Blazor, we’d love to hear it!

  • Check out the features or bugs others have reported and vote on your favorites. Feedback will be prioritized based on popularity.
  • If you have feedback that’s not listed yet, submit your own.

Thanks for joining our community and helping improve Syncfusion products!

4
Votes

This is a bug, not feature request.

Please see here for history of this ticket:

https://www.syncfusion.com/feedback/32673/crash-after-navigating-from-dashboard-layout-to-another-page


I believe that OP explains it well:

After navigating from a page with Dashboard layout component to another page sometimes (1 out of 10-20 times) application crashes with exception:

Error: System.NullReferenceException: Object reference not set to an instance of an object. at Syncfusion.Blazor.Layouts.SfDashboardLayout.SetHeightWidth() at System.Threading.Tasks.Task.<>c.<ThrowAsync>b__128_0(Object state) at Microsoft.AspNetCore.Components.Rendering.RendererSynchronizationContext.ExecuteSynchronously(TaskCompletionSource`1 completion, SendOrPostCallback d, Object state) at Microsoft.AspNetCore.Components.Rendering.RendererSynchronizationContext.<>c.<.cctor>b__23_0(Object state) at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state) --- End of stack trace from previous location --- at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state) at Microsoft.AspNetCore.Components.Rendering.RendererSynchronizationContext.ExecuteBackground(WorkItem item)


This exception cannot even be prevented with the latest .NET 6 feature "Error boundaries". So can you please take a look on this and add null reference check. Also possible solution can be to remove 'async void' construction and make a method 'async Task', so error boundaries can catch this exception.