Radzen pager infinite loop

Radzen.Blazor Components
1

There seems to be an issue with the data grid pager component when the DataGridSettings have a CurrentPage set to larger than the number of pages available.

I am able to replicate this with 2 scenarios:

  1. Save DataGridSettings for a large data set with a high CurrentPage value. Clear table settings, load in a smaller data set (or empty the table) then reapply the saved DataGridSettings

  2. Load a large data set and select a high CurrentPage. Then replace the data set with a smaller set that doesn't have the current page available.

In both scenarios, the app will run at max CPU and memory usage ramps quickly to 4GB and on. There is no fix other than to force close the application.

I have resolved scenario 1 by forcing CurrentPage to 0 before applying saved DataGridSettings but thought this might be affecting other users so should be raised

2

If you believe that you have fix for an issue you can submit pull request. We will review your update and if everything works correctly we will merge it.

3

Sorry, its not a fix in the Radzen code, I just force the saved DataGridSettings.CurrentPage value to 0 in my code before applying them to the Data Grid thus making DataGridSettings.CurrentPage redundant in my app.