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
I'm getting memory leaks every time I expand and collapse nodes of the TreeView control. When I instantiate a TreeView control and simply expand and collapse nodes repeatedly, the memory footprint grows and grows and never gets garbage collected.
Also, the TreeView isn't getting garbage collected when the control is removed. The memory snapshot below shows:
-> three valid instances of the TreeView control and
-> two invalid instances of the TreeView control ("HashSet+Entry[ ]") that were instantiated in popups, which were later closed.
The two invalid instances of the TreeView control persist and cannot be garbage collected, apparently due to some reference to MobileTap? Before closing the popup, I have tried setting many of the TreeView (and ViewModel) properties to null. Before closing the popul, I also I tried expressly removing the TreeView control and setting its instance = null. However, none of these attempts have enabled the garbage collector to eliminate the TreeView control.
Is anyone else experiencing these problems?
Or does anyone have any suggestions for how to stop these problems?
I'm guessing that the TreeView wants a .Dispose() method that cleans up everything.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
I'm getting memory leaks every time I expand and collapse nodes of the TreeView control. When I instantiate a TreeView control and simply expand and collapse nodes repeatedly, the memory footprint grows and grows and never gets garbage collected.
Also, the TreeView isn't getting garbage collected when the control is removed. The memory snapshot below shows:
-> three valid instances of the TreeView control and
-> two invalid instances of the TreeView control ("HashSet+Entry[ ]") that were instantiated in popups, which were later closed.
The two invalid instances of the TreeView control persist and cannot be garbage collected, apparently due to some reference to MobileTap? Before closing the popup, I have tried setting many of the TreeView (and ViewModel) properties to null. Before closing the popul, I also I tried expressly removing the TreeView control and setting its instance = null. However, none of these attempts have enabled the garbage collector to eliminate the TreeView control.
Is anyone else experiencing these problems?
Or does anyone have any suggestions for how to stop these problems?
I'm guessing that the TreeView wants a .Dispose() method that cleans up everything.
All reactions