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 months 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
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 2 months ago
- last edited 2 months ago
- Hi Eamon, Thank you for the update. Please be informed that the reported issue has been prioritized on our side, and our developers will have a look at it as soon as they finish the currently assigned tasks. 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 2 months ago
- Hi, as I’ve mentioned in the following forums thread: https://www.scichart.com/questions/wpf/how-can-you-ensure-that-boxplot-series-on-different-axes-have-the-same-width, – the reported issue has been fixed in SciChart v8.6.0.28230 Hotfix version. So please feel free to try it out. Kind regards, Lex
We tried the latest version available on myget but we still have the same issue.- Hi, Thanks for your reply. The same exception message can be triggered by various issues. We would appreciate it if you could share all the issue details, including the small sample project reproducing it, the steps to produce it, and your hardware details (e.g., GPU models), in the support request you’ve recently submitted. This would help us keep all the required information in one place and ease tracking of the conversation. Thanks in advance, Lex
- You must login to post comments
Hi Eamon,
Hope you are doing well.
Unfortunately, we can’t reproduce the reported issue on any available hardware anymore after the last December 2024 Windows patch.
Could you please try updating your system, including the latest Windows updates and GPU driver versions, and let us know if you are still experiencing the same issue?
Kind regards,
Lex
- Lex answered 3 weeks ago
- last edited 3 weeks ago
- However, we’ve modified the example project with the custom VX Render Surface. It’s fixing one of the possible causes of the reported issue. Please try it out and let us know your feedback.
- You must login to post comments
I have just done all available updates to the PC through windows update and also installed the latest drivers from AMD and the leak persists.
- Eamon answered 3 weeks ago
I have just tried your modified example project and can confirm that it resolves the leak. Is this “fix” likely to make it into a new build soon?
- You must login to post comments
Please login first to submit.
