Memory leak in Fifo mode with Visual Xccelerator Engine enabled.
Two screenshots with Visual Xccelerator Engine enabled and disabled.
In a real application, the behavior is repeated. GS.Collect does not solve the problem.
It looks like the problem occurs on the integrated video card. AMD. When switching to a discrete video card. Memory is stable.
- p0934181372 p0934181372 asked 1 year ago
- last edited 1 year ago
-
Thanks for the bug report. Reproduction steps? Just run the example and wait?
- You must login to post comments
Running this now
My steps to reproduce.
- I started SciChart WPF 7.0.1 Examples App / .NET 4.6.2 version
- Attached dotTrace Memory Profiler
- Switched to the FIFO Scrolling Charts example
- Wait a few minutes
Application memory seems rock solid stable at 595 – 600 MBytes.
Are there any specific steps to reproduce this?
Best regards
Andrew
- Andrew Burnett-Thompson answered 1 year ago
- last edited 1 year ago
- You must login to post comments
It’s like that. I just ran the SciChart WPF v7 Examples (.NET 6.0 Windows) version. Checked on NetFramework, the problem was repeated.
- p0934181372 p0934181372 answered 1 year ago
- last edited 1 year ago
- You must login to post comments
It looks like the problem occurs on the integrated video card. AMD. When switching to a discrete video card. Memory is stable.
- p0934181372 p0934181372 answered 1 year ago
- last edited 1 year ago
-
That’s interesting. What graphics card / driver version?
- You must login to post comments
In this case, there is no leakage. AMD Radeon disabled. The driver has been updated to the latest version. Prior to that, there was a version for the month of February. Problem still exists.
Based on the checks, it turns out that the leak occurs when 2 video cards are turned on.
- p0934181372 p0934181372 answered 1 year ago
- last edited 1 year ago
-
OK if you have a memory leak occurring in one specific GPU then it likely it is a driver problem, not a SciChart problem. My suggestion is contact the video card manufacturer with an executable that reproduces the problem and they should respond. We’ve done this for Intel GPUs and they do listen!
- You must login to post comments
Please login first to submit.