This thread looks to be a little on the old side and therefore may no longer be relevant. Please see if there is a newer thread on the subject and ensure you're using the most recent build of any software if your question regards a particular product.
This thread has been locked and is no longer accepting new posts, if you have a question regarding this topic please email us at support@mindscape.co.nz
|
Hi There, As in thread http://www.mindscapehq.com/forums/thread/1588525, the chart on Version 6 also has some memory leak as in screen shot included. Same operation and same code in version 5.0 does not have same problem. Please fix them. Thanks, Gordon |
|
|
|
|
Hello Gordon I have not been able to reproduce this charting memory leak. This has either been resolved as a result of the DataGrid memory leak fix, or this could be a memory leak introduced at your end. Looking at the image you posted, the chart is being held by the visual tree. This is usually an indication that the memory profiler snapshot occurred before the GC finished, or the page is still being held by something in your application. Let me know if you have more information after the next nightly build. -Jason Fauchelle |
|
|
|
|
Hi Jason, I downloaded Jan 21, 2014 nightly build and the leaks is still there. Our code does not change between we use version 5.0 and Version 6.0 except the changes with GridLength for column width and object for min/max value. But same operation same code, version 5.0 has no problem. If you want I can give you the memory profile for both 5.0 and 6.0 in our application. From the screen shot on this thread, it has something on DualSlider. Thanks, Gordon |
|
|
|
|
Hello Gordon The DualSlider is simply being held onto by the Chart, this is normal. The problem is what is holding on to the chart? Please provide steps to reproduce this memory leak. Looks like this might be very application specific though. -Jason Fauchelle |
|
|
|
|
Hi Jason, As I explained before, same code same operation the version 5.0 is OK, but not veriosn 6.0. To convince you, I will have reproduce project and the following are the steps: 1) unzip the file, you may need to change the reference for mindscape dll to your proper address 2) Build application (build it into Any CPU) 3) Run Ants Memory Profile, and point the .Net Executable to this exe 4) Click on butoon "Grid and Chart" 5) Click on 3rd row on the top datagrid, with Name "test2", you will have Graphics to show on the button and UserControl name for the bottom is: "UserControlContinusData" 6) Now, Click on 4th record with name "Non Param", the bottom is going to show a textblock and UserControlContinusData will not be needed. 7) Take a memory snapshot from the profile On the class list, find UserControlContinusData and you will find the memory leak there. Some times it is very hard to get reproduce project and one of our team member does not allow me to send you whole project executable since it is related to the product privacy protection. I understand your position and hope you understand what I am going through when you told me you cannot reproduce the problem. Thanks, Gordon Thanks, Gordon |
|
|
|
|
Hello Gordon Thanks for the repro project! I certainly understand what it is like when you need to build a repro project. This memory leak will be resolved in the next nightly build. -Jason Fauchelle |
|
|
|
|
Thanks Jason. It is fixed in Jan 22, 2014 version. Gordon |
|
|
|
