I was able to reproduce the issue and fix the problem. There was an issue with full chart refreshes (such as when you set RefreshEnabled = false and then true or call Refresh() ) where some event listeners were being leaked.

In the interim, its best to avoid causing full chart refreshes with too great a frequency (Calling Refresh() or toggling RefreshEnabled, etc.)

The resolution to this issue should be available with the next service release.

Graham,

Sorry for the late reply. You can reproduce the memory issue using sample code which was provided by your team in this posting.

Regards,

Madhan

Thanks for providing more info. I'll see if I can replicate the issue.

Hi,

I have the same problem of memory leak. to reproduce it, it's easy:

Create a simple chart in xaml:

<Grid x:Name="LayoutRoot" Background="White">
        <Border Height="Auto" Width="Auto" VerticalAlignment="Top" BorderThickness="1,1,1,1" BorderBrush="White" Margin="0,10,0,0">
            <StackPanel Height="Auto" Width="250" Margin="0,0,0,0">
                <Canvas x:Name="ChartCanvas0" Width="334" Height="368" HorizontalAlignment="Center">

<Chart:XamWebChart x:Name="ChartControl0" 
                                       Height="364"
                                       Width="366"
                                       BorderThickness="0"
                                       Canvas.Left="-24" Canvas.Top="5">
                        <Chart:XamWebChart.Legend>
                            <Chart:Legend Visibility="Collapsed"/>
                        </Chart:XamWebChart.Legend>
                    </Chart:XamWebChart>
                </Canvas>
            </StackPanel>
        </Border>
    </Grid> 

In the "code - behing", create a timer who update the seriescollection each 5s:

private void RefreshData()
{
            IsRefreshable = false;
            Curves = GetData();
            IsRefreshable = true;
}

//it's just an example 

private SeriesCollection GetData()
        {
          
            SeriesCollection sColl = new SeriesCollection();

            for (int i = 0; i < 7; i++)
            {
                Series s = new Series();
                s.ChartType = ChartType.ScatterLine;
                ObservableCollection<DataPoint> lData = new ObservableCollection<DataPoint>();
                for (int j = 0; j < 200; j++)
                {
                    DataPoint d = new DataPoint();
                    d.ChartParameters.Add(new ChartParameter
                    {
                        Type = ChartParameterType.ValueY,
                        Value = i

                    });
                    d.ChartParameters.Add(new ChartParameter
                    {
                        Type = ChartParameterType.ValueX,
                        Value = j

                    });
                    lData.Add(d);
                }
                s.DataPoints = lData;
                sColl.Add(s);
            }
            return sColl;
        }

If you check your perfmon or taskmgr, you can see that the memory of the process iexplorer increase for each time you are updating the series of the chart. After some times, an "Outofmemory exception" is throwed by the application.

if you changing the code by just only updated the datapoint or chartparameter, it's the same result.

or, if you binding the seriescollection(MVVM), same result.

The garbageCollector never cleans the old objects.

Have you got an answer for this problem?

Thank you for your quick answer.

Some additional performance hints for the chart:

1. Try to minimize the number of axis labels being drawn if you have lots of charts on the page. The chart does complex collision routines to attempt to adjust label sizing etc. So the less axis labels you are rendering in total, the better. The easiest way to adjust the number of axis labels you are displaying is to adjust the Minimum, Maximum, Unit, and AutoRange properties of the axis.
2. If at all possible set the Fill on the Series or the DataPoints locally rather than letting the auto-coloring take effect. The current auto-coloring implementation needs to clone a lot of brushes to work which will negatively affect the performance of the chart.
3. We're in the process of resolving some Databinding performance issues that occur even if you set RefreshEnabled = false during a mass update. Once these are resolved you will only need to toggle this property when doing a mass update, but until then its more performant to populate and update the Datapoints directly when making large changes.

-Graham