Memory leak in datatable when using it inside iFrame
Memory leak in datatable when using it inside iFrame
muthu211
Posts: 1Questions: 0Answers: 0
Hi Alan,
We are using datatable (1.9.4) and we have few entry fields in each row of the data table.
When the same datatable is being called outside iFrame, there is no subsequent memory increase.
However, when the same datatable is embeded inside iFrame, on each action performed on the user controls in the datatable, there is a subsequent increase in memory and the memory is not dropping down until the browser is closed.
We tried the following options
1) Used fndestroy() - however, this was not suited to our requirement as it cleared the entire table.
2) included bdestroy property - This was not impacting our requirement, but it also didnt brought the memory down.
3) we tried unbind the event listners option $(oSettings.nTableWrapper).find("*").andSelf().unbind(); (as per your suggestion in another discussion)
However, all the above options were not giving a hope.
Kindly suggest us on any other alternate approach to bring down the memory.
Cheers,
Muthu.
We are using datatable (1.9.4) and we have few entry fields in each row of the data table.
When the same datatable is being called outside iFrame, there is no subsequent memory increase.
However, when the same datatable is embeded inside iFrame, on each action performed on the user controls in the datatable, there is a subsequent increase in memory and the memory is not dropping down until the browser is closed.
We tried the following options
1) Used fndestroy() - however, this was not suited to our requirement as it cleared the entire table.
2) included bdestroy property - This was not impacting our requirement, but it also didnt brought the memory down.
3) we tried unbind the event listners option $(oSettings.nTableWrapper).find("*").andSelf().unbind(); (as per your suggestion in another discussion)
However, all the above options were not giving a hope.
Kindly suggest us on any other alternate approach to bring down the memory.
Cheers,
Muthu.
This discussion has been closed.