Hi, have used a memory profiler on a project which has revealed a memory leak for my app. The issue is that when I remove nodes from the UltraWinTree references to these removed nodes are still being held in the private visibleNodes variable of type VisibleNodesManager within the UltraWinTree. Is there a way for me to 'refresh' this list? I cannot find any method which might help in this regard. Or, could anyone suggest a workaround for this?
I am using version 6.1.20061.1069 of the UltraWinTree.
Many thanks in advance.
Pete.
Hi Pete,
Without a sample to reproduce the problem, I can only guess, but I did look at the source code and there was an issue where the VisibleNodesManager would hold on to references to nodes that were removed from the tree and that issue was fixed in 8.3 and up, so it should be fixed in 9.2. If you are still experiencing an issue, then I will need to be able to reproduce the issue you are seeing in order to figure out what's going on.
Can you reproduce the problem in a small sample project and post it here along with your results so I can check it out?
I've looked more closely at my Infragistics account downloads and I've access to 2009 Vol 2, which I've upgraded my project to. This gives me version 9.2.20092.1003 of the UltraWinTree.
BUT, the same memory leak problem STILL exists in this version, despite you saying it was fixed in v8.3 and up!!!???
Can you please offer some help or a solution?
Hi, thanks for the information.
Am I able to upgrade to a version that's rid of this bug for FREE?
It would seem a bit rich to ask my company to pay more money to overcome a bug infragistics caused.
Kind regards
I took a look at the code and as far as I can tell, there's no way to work around this. But the issue was fixed around 2009 (in v8.3 and up). So if you update the latest version (2016.1), this should no longer be a problem.