You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When using "replaceData" many times with an heavy dataload on Tabulator 5.x and 6.2 with dataTree activated, Chrome crashed sometimes out of memory.
With a bit of investigation, I found that when calling "replaceData", old rows are deleted (wipe), but expanded row's cells aren't.
So Tabulator's table.columnManager stills reference old detached DOM cells, and memory is growing without limit.
The problem occurs only if some row are expanded. If I don't have any dataTree or if I force all row to be 'closed' this leak doesn't occur.
Describe the bug
When using "replaceData" many times with an heavy dataload on Tabulator 5.x and 6.2 with dataTree activated, Chrome crashed sometimes out of memory.
With a bit of investigation, I found that when calling "replaceData", old rows are deleted (wipe), but expanded row's cells aren't.
So Tabulator's table.columnManager stills reference old detached DOM cells, and memory is growing without limit.
The problem occurs only if some row are expanded. If I don't have any dataTree or if I force all row to be 'closed' this leak doesn't occur.
Tabulator Info
6.2
Working Example
I've made an super simple example:
https://jsfiddle.net/Lionel_Anyware/nmsk6jq5/6/
To Reproduce
A step by step guide to recreate the issue in your JS Fiddle or Codepen:
Expected behavior
The dataTree's children cells (if I understand correctly) should be deleted as well as rows.Cells when calling replaceData
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: