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
Expand row 1 followed by row 2 (possibly followed by row 3)
Observe the page freezes
Eventually the error will show in dev tools
VirtualDomVertical.js:92 Uncaught RangeError: Maximum call stack size exceeded
at VirtualDomVertical.js:92:17
at Array.forEach (<anonymous>)
at b.rerenderRows (VirtualDomVertical.js:92:8)
at f.reRenderInPosition (RowManager.js:854:18)
at f.redraw (RowManager.js:1116:9)
at ResizeTableModule.tableResized (ResizeTable.js:138:25)
at InternalEventBus.js:119:25
at Array.forEach (<anonymous>)
at R._dispatch (InternalEventBus.js:118:21)
at f.dispatch (CoreFeature.js:78:30)
Desktop (please complete the following information):
OS: Mac
Browser: Chrome
Version: 129
Additional context
It doesn't seem to be a problem in 5.x
The text was updated successfully, but these errors were encountered:
s-cork
changed the title
DataTree rendering bug causes maximum call stack size
DataTree rendering can result in maximum call stack size exceeded
Oct 15, 2024
i just tried the fiddle with the patched version of #4598 and it seems to be fixed by that, so the expanding/collapsing triggers the same recursive rendering behavior as in #4467
Describe the bug
Enough TreeData when expanded can cause Uncaught RangeError: Maximum call stack size exceeded
Tabulator Info
6.3.0
Working Example
To Reproduce
A step by step guide to recreate the issue in your JS Fiddle or Codepen:
Desktop (please complete the following information):
Additional context
It doesn't seem to be a problem in 5.x
The text was updated successfully, but these errors were encountered: