Hello,
it seems that there is a client side memory leak in the asp.net telerik controls. We tested this with 2019.3.1023 (the current release).
You can reproduce the leak also with the telerik demo:
https://demos.telerik.com/aspnet-ajax/grid/examples/functionality/filtering/excel-like-filtering/defaultcs.aspx
It seems to depend on the excel like filtering, so you have to use this demo. The memory leak doesn't exist in basic filtering.
Each time you make a postback, e.g. use the pager, the browser holds a reference of the "old" grid in memory. Because of this the browser seems to hold the old html elements (orphaned nodes).
Can you confirm the problem and is there a fix available?
Regards
it seems that there is a client side memory leak in the asp.net telerik controls. We tested this with 2019.3.1023 (the current release).
You can reproduce the leak also with the telerik demo:
https://demos.telerik.com/aspnet-ajax/grid/examples/functionality/filtering/excel-like-filtering/defaultcs.aspx
It seems to depend on the excel like filtering, so you have to use this demo. The memory leak doesn't exist in basic filtering.
Each time you make a postback, e.g. use the pager, the browser holds a reference of the "old" grid in memory. Because of this the browser seems to hold the old html elements (orphaned nodes).
Can you confirm the problem and is there a fix available?
Regards