Pre loader

Memory leak in Fifo mode with Visual Xccelerator Engine enabled

Welcome to the SciChart Forums!

  • Please read our Question Asking Guidelines for how to format a good question
  • Some reputation is required to post answers. Get up-voted to avoid the spam filter!
  • We welcome community answers and upvotes. Every Q&A improves SciChart for everyone

WPF Forums | JavaScript Forums | Android Forums | iOS Forums

1
0

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.

Version
7
Images
  • You must to post comments
1
0

It’s like that. I just ran the SciChart WPF v7 Examples (.NET 6.0 Windows) version. Checked on NetFramework, the problem was repeated.

Images
  • You must to post comments
1
0

It looks like the problem occurs on the integrated video card. AMD. When switching to a discrete video card. Memory is stable.

  • You must to post comments
1
0

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.

enter image description here

Are there any specific steps to reproduce this?

Best regards
Andrew

  • You must to post comments
0
0

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.

Images
  • Andrew Burnett-Thompson
    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 to post comments
0
0

Hello, I stumbled upon this issue only recently after upgrading to version 8. What I found is that I have no issues with version 7 but the same issues can be reproduced in version 8 and are not limited to the FIFO example and can be reproduced even in static charts by simply zooming in and out.

Second thing that I found is that this memory behaviour is limited to the DirectX 11 in version 8. When switched to the DirectX 9c memory is stable.

I have only integrated AMD GPU and have latest drivers as of early June 2024. This makes version 8 somewhat unusable for us as we found other stability issues when forced to DX9.

Images
  • Lex
    Hi Jakub, Thank you for reporting this. I am sorry for the late reply. The original post was related to SciChart v7. So it looks like you are experiencing a slightly different issue. Could you please provide us with steps to reproduce this issue in one of our examples from the WPF Examples suite or share a small sample project reproducing this for investigation on our side? Please also share a screenshot showing the memory profiling results. Thanks in advance, Lex, SciChart Technical Support Engineer
  • You must to post comments
Showing 5 results
Your Answer

Please first to submit.