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
Reported by @mraleph. Reading the code, there should be a memory leak when detaching a sub-tree of RenderNodes. Despite Detach() nulling out _parent for the top-most detached child, the cycles inside the sub-tree should still prevent the destructors from being called. A quick speculative fix is to override Detach() in RenderMultiChildParent and call Detach() recursively on all live children.
The text was updated successfully, but these errors were encountered:
Reported by @mraleph. Reading the code, there should be a memory leak when detaching a sub-tree of
RenderNode
s. DespiteDetach()
nulling out_parent
for the top-most detached child, the cycles inside the sub-tree should still prevent the destructors from being called. A quick speculative fix is to overrideDetach()
inRenderMultiChildParent
and callDetach()
recursively on all live children.The text was updated successfully, but these errors were encountered: