Run a time series playthrough in the test viewer. In Chrome devtools memory profiler you can see heap allocations every time new volume data is swapped in. The retained objects are nearly all from tweakpane.
Expected Behavior
Playing through time series should not cause the js heap graph to rise.
Possible workaround: do we even need to rebuild the tweakpane every time data arrives? Best solution would be to be able to properly clean up the tweakpane, or understand why we can not.
Description
Run a time series playthrough in the test viewer. In Chrome devtools memory profiler you can see heap allocations every time new volume data is swapped in. The retained objects are nearly all from tweakpane.
Expected Behavior
Playing through time series should not cause the js heap graph to rise.
Possible workaround: do we even need to rebuild the tweakpane every time data arrives? Best solution would be to be able to properly clean up the tweakpane, or understand why we can not.