We have discovered that Scichart is leaking memory on one of our machines.
Setting VisualXcceleratorEngine.IsEnabled=false prevents the memory leak.
In trying to produce a minimum reproduction I found that all I needed was a blank new WPF project with an empty SciChartSurface on it (https://grinstallers.blob.core.windows.net/public/Scichart%20Memory%20leak.zip as it would not let me attach it here).
Simply resizing the window would cause the leak. I have linked to a screen recording showing the leak occurring in real-time (https://grinstallers.blob.core.windows.net/public/Screen%20Recording%202024-11-21%20132048.mp4). The machine with the issue has an AMD Radeon RX 640 video card and I do not get the same leaking behaviour on another machine with Intel UHD Graphics 770. I have updated all drivers to the latest version and the leak still happens.
A memory dump of the process shows the majority of memory is unmanaged (Managed heap = ~450MB of 10GB).
I have gone back as far as version 8.0.0.27737 and the leaking behaviour is still there.
- Eamon asked 2 weeks ago
Hi Eamon, Thank you for reporting this. I am going to investigate the shared sample project and will get back to you as soon as I have an update. Kind regards, Lex, SciChart Technical Support Engineer- Hi Eamon, I managed to reproduce the reported issue on our side. It doesn’t seem to be a hardware-dependent issue though because I reproduced it both with RTX 3070 and integrated AMD Graphics. However, I’ll forward this to our developers for further investigation. Kind regards, Lex
- You must login to post comments
We also have this memory issue.
Just for our information, when can we expect a new release?
Because between the AccessViolationException (https://www.scichart.com/questions/wpf/how-can-you-ensure-that-boxplot-series-on-different-axes-have-the-same-width) and the OutOfMemoryException we have for months now (hopefully not on all computers), we’re wondering if we should not try to downgrade to v.7 or even v.6 :-(.
But if a new release is coming soon, we’ll try that first.
- AC42admin LMB answered 1 week ago
- You must login to post comments
Hi Lex, thanks for the confirmation.
This is fairly high priority for us as this leak results in our application growing it’s memory footprint to about 120GB commit size before crashing with out-of-memory exceptions within about 24 hours.
- Eamon answered 1 week ago
- last edited 1 week ago
- You must login to post comments
Please login first to submit.
