SciChart® the market leader in Fast WPF Charts, WPF 3D Charts, and iOS Chart & Android Chart Components
Please use the forums below to ask questions about SciChart. Take a moment to read our Question asking guidelines on how to ask a good question and our support policy. We also have a tag=SciChart on Stackoverflow.com where you can earn rep for your questions!
Please note: SciChart team will only answer questions from customers with active support subscriptions. Expired support questions will be ignored. If your support status shows incorrectly, contact us and we will be glad to help.
It seems that fifo dataseries has slow memory leak.
Try open new thread window and launch fast fifo series update. Wait long time(1-5 days). See that memory slowly grows up. Dispose the window and see that memory not garbage collected.
It was 3 surfaces on one window with 3 dataseries on each surface(9 total).
Append timeframe was 10 points each 100 ms on each serie. Fifo capacity 10 000. (900 points per second and 90 000 points total in fifo buffers each moment)
After 5 days OutOfMemoryException was thrown. 1Gb was allocated in 32bit application.
Hi Nikita, First of two memory leaks reported has been fixed (SciChartSurface/DataSeries staying in memory after chart window closed). Please find the hotfix v126.96.36.1990 at http://www.scichart.com/downloads. Also this version contains RolloverModifier X/Y values and there is a forum post on this here: http://http://www.scichart.com/questions/question/rolloverlabeltemplate-show-x-and-y-value-separated/
There was a bug in the UpdateSuspender returned from sciChartSurface.SuspendUpdates() which was keeping axes alive after removing. Axes had a reference to the DataSet so the dataseries were never collected. Opening/closing chart panes now correctly releases memory.
The second issue (FIFO Series) we are investigating but as yet are unable to find any obvious flaw with memory usage.
Since v1.3 there have been many memory leaks found and fixed. We also have a blog post here on diagnosing a leak and suggestions for clearing it.
Please login first to submit.