I am seeing the working set of iexploere.exe increase at the rate of 10MB/hr when receiving 1 data point/sec/series with 2 series on the chart. This seems to go on until IE crashes ~1.2GB in size.
I create each series dynamically and if I simply comment the ItemSource out of each series leaving in all other code the memory does not increase at all. I realize that is a BIG change but it does seem to point to the rendering/binding of the series as the culprit for the leak.
In a previous post I was told the there was an issue with the way the axis label settings we bound but that was over a year ago. Do you know if there is still a similar leak in the 11.1 version of the product?
Mike,
Its also possible there is some sort of regression. I'll see if I can reproduce it, but if you have a simple sample that can reproduce the issue, that would certainly help.
Thanks,
Graham
I just made some quick changes to my code that I thought would have very little effect on memory and this appears to have stopped the leak. I am running the app overnight to see how it fares but this post may have been a false alarm. I'll post again in the morning with my results.
If you figure out what you changed to avoid the problem. It would be good to know, as it could point to a leak we have to resolve somewhere for that particular use case. Glad you got it worked out!
-Graham
Well preliminary testing is showing that the majority of the memory leak has been corrected by doing things that we should no longer have to do in .Net. In all functions I set all local variables to null at the end and switched to passing by ref wherever possible (not really sure this specific change made a difference though). It appears to reduce the leak by 90%. I thought .Net was supposed to clean up local variables once they go out of scope but perhaps we have too much going on for the garbage collector to keep up with to our satisfaction.