Hi,
we noticed a severe issue of memory leak using a binded UltraWinTree; our tree is binded to a collection of classes: we fill in and empty this collection but when this collection is empty, classes previously showed in the tree (and then disposed) remain alive. It seems that the tree element stores a pointer to the classes inside an internal field named nodeClientAreaUIElement
Note : we don't have to dispose the tree until the program is closed because its possible to refill the collection more times.
In attach a little sample reproducing our issue.
Is there a solution to avoid this issue? Will it be fixed in the future releases ?
Best regards
Hello,
You are right, I tested this and it turned out that it is an already fixed issue and is fixed in the latest service release available for you current version, so please download it and test your application against it.