ArgumentOutOfRangeException When Filtering & Clicking Grid

[Richard]

I'm having an intermittent issue since upgrading to the latest 2016 R3. 

Sometimes when filtering a grid and then clicking a row in that grid I get a '[Arg_ArgumentOutOfRangeException]' exception. My application has many grids and they all seem to be affected. I don't think it was an issue before R3 but it is very rare so its hard to say for certain when it started. 

I understand I'm not giving you much to go on here but I can barely recreate the issue myself. About 1 in 20 times I filter my grid and then click on a row I'll get this error. 

Here is some of the stack trace I retrieved, any help at all would be greatly appreciated. 

Richard

[Arg_ArgumentOutOfRangeException]
Arguments: 
Parameter name: count

at System.Linq.Enumerable.Range(Int32 start, Int32 count)
at Telerik.Windows.Controls.GridView.Selection.CellRegionsPartitioner.CalculateAffectedRegions(Pair`2 firstAndLastSelectedIndices, Int32 columnCount)
at Telerik.Windows.Controls.GridView.Selection.CellRegionsPartitioner.CalculateAffectedRegions()
at Telerik.Windows.Controls.GridView.Selection.CompositeSelectionHandler.UpdateSelectedCells(IList`1 items, Boolean isSelected)
at Telerik.Windows.Controls.GridView.Selection.CompositeSelectionHandler.UpdateCellSelectionOnSelectedItemsChanged(SelectionChangeEventArgs selectionChangeArgs)
at Telerik.Windows.Controls.GridView.Selection.CompositeSelectionHandler.OnOwnerSelectionChangedDispatch(Object sender, SelectionChangeEventArgs e)

[Yoan]

Hello Richard,

We had fixed similar problem recently. You can download our latest internal build and give it a try. Please let us know about the result.

Regards,
Yoan
Telerik by Progress

[Richard]

Thanks Yoan, 

I'll try the latest build and see how I get on, I'll mark this answered if I don't get the issue again for the next few days. 

Richard 

[Yoan]

Hello Richard,

I will close this thread for now. Please, do not hesitate to open it if you encounter any problems.

Regards,
Yoan
Telerik by Progress

[Richard]

Hi Yoan,

Yes, the latest internal build seems of have fixed the issue.

Thanks,

Richard