-
Notifications
You must be signed in to change notification settings - Fork 821
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Growing snapshot heap on continuous data update with data containing children #4668
Comments
Our current fix is in
whereas the method is called in
|
The HTML file used for the local reproduction is:
|
Hey @mkempf Thanks for the headsup, i have pushed a fix for this to the master branch and will include it in todays patch release. Cheers Oli :) |
Hi @olifolkerd thanks a lot for the fast fix and the patch release. thanks again |
Describe the bug
Continuously setting new data or slightly changed new data by using
setData
method increases the snapshot heap of the site. It only happens when the rows contain child rows.Tabulator Info
Working Example
To Reproduce
There are detached div elements. Most probably from child cells / rows.
Repeating step 3 several times makes the growing memory more obvious.
Expected behavior
Snapshot heap is not continuously growing when pressing 'Update Data' several times
Screenshots
The following screenshot shows the detached elements in a comparison of two heap snapshots after clicking once on the 'Update Data' button. Be aware that the heap snapshot is done locally as in JSFiddle the snapshot heap of the iFrame seems not to be captured.
Desktop (please complete the following information):
Additional context
We figured the leak only because of a table with lots of and nested children rows that are continuously updated. The site is currently running out of memory quite fast.
The text was updated successfully, but these errors were encountered: