I'm encountering an issue in my Blazor application where rapid page navigation seems to be causing problems. Each page in my application initializes Entity Framework Core to fetch data from the database. However, if I navigate between pages quickly before Entity Framework Core completes its operation, it causes the page to break, throwing errors like
Invalid attempt to call ReadAsync when reader is closed
I suspect that this issue might be related to the way Blazor handles page initialization and disposal, possibly causing conflicts with Entity Framework Core's database connections.
Has anyone else experienced a similar issue? What could be causing this behavior, and how can I address it to ensure smooth page transitions even with rapid navigation?
Microsoft.AspNetCore.Components.Server.Circuits.CircuitHost[111] Unhandled exception in circuit 'DGk_KNxu7rKw9J-WL_-4ZPD8OV3XvTtepIKWTAk2_GI'. System.InvalidOperationException: Invalid attempt to call ReadAsync when reader is closed. at Microsoft.Data.Common.ADP.ExceptionWithStackTrace(Exception e) --- End of stack trace from previous location --- at Microsoft.EntityFrameworkCore.Query.Internal.SingleQueryingEnumerable`1.AsyncEnumerator.MoveNextAsync() at Microsoft.EntityFrameworkCore.EntityFrameworkQueryableExtensions.ToListAsync[TSource](IQueryable`1 source, CancellationToken cancellationToken) at Microsoft.EntityFrameworkCore.EntityFrameworkQueryableExtensions.ToListAsync[TSource](IQueryable`1 source, CancellationToken cancellationToken) at cpServicios.Services.PacientesServices.GetAllPacientes() in C:\Users\PC\Documents\Proyectos\cdeWebApp\cpServicios\Services\Pacientes\PacientesServices.cs:line 51 at cdeWebApp.Components.Pages.Tablas.TablaPacientes.OnInitializedAsync() at Microsoft.AspNetCore.Components.ComponentBase.RunInitAndSetParametersAsync() at Microsoft.AspNetCore.Components.RenderTree.Renderer.GetErrorHandledTask(Task taskToHandle, ComponentState owningComponentState)