George Henderson
George Henderson
The issue seems to be centered around this effect. It causes the component tree to render when it sets the tree state inside of the effect. You essentially set state...
Are there any workarounds for this issue? Is it possible to manually cleanup a tree and then reset with a new root cursor. Currently running into memory issues with SSR,...
There seems to be a memory leak when just resetting the tree using `tree.set()`. Should that remove all of the old event listeners too, like release does?
Its not costly from a performance standpoint, more from a application refactor perspective. Currently I am exporting my tree in a module that the rest of my application is referencing...
yes, something similar to what christianalfoni recommended with `tree.mute() // removes listeners`.
Great! thanks will give it a try.
Yeah, I'm seeing issues with this method. It looks like its from old selections.
What are the down sides to using `tree.unbindAll()`? Will that still leave around old data if we then call `tree.set()`. Seems to work but can't tell if there is still...
Great thank you for your help and contributions to OS, baobab is bad ass.
Or maybe more generic like: ```javascript asyncComponent({ ... onResolve: () => AnotherAsyncComponent.resolve() }) ```