Please answer.
When upgrading from 6.5.0.13720 to 6.5.1.26063, an error now occurs.
This does not occur with 6.5.0.13720.
The error seems to occur just before drawing the graph.
The errors that occur are as follows.
Exception: System.AccessViolationException: Attempted to read or write
protected memory. This is often an indication that other memory is
corrupt.SciChart.Charting2D.Interop.SCRTWPFInterop.CreateRenderTarget(int,
int)
SciChart.Drawing.VisualXcceleratorRasterizer.VisualXcceleratorRenderSurface.RecreateSurface()
SciChart.Drawing.Common.RenderSurfaceBase.hpy(object, System.Windows.SizeChangedEventArgs)
System.Windows.RoutedEventArgs.InvokeHandler(System.Delegate, object) at: RoutedEventArgs.cs
System.Windows.RoutedEventHandlerInfo.InvokeHandler(object, System.Windows.RoutedEventArgs) at: RoutedEventHandlerInfo.cs
System.Windows.EventRoute.InvokeHandlersImpl(object, System.Windows.RoutedEventArgs, bool) at: EventRoute.cs
System.Windows.UIElement.RaiseEventImpl(System.Windows.DependencyObject,
System.Windows.RoutedEventArgs) at: UIElement.cs
System.Windows.FrameworkElement.OnRenderSizeChanged(System.Windows.SizeChangedInfo)
at: FrameworkElement.cs
System.Windows.ContextLayoutManager.fireSizeChangedEvents() at: LayoutManager.cs
System.Windows.ContextLayoutManager.UpdateLayout() at: LayoutManager.cs
…
This does not happen if you reduce the amount of data displayed on the graph.
Even if the following processing was implemented just before the error occurred, it did not improve.
Would you like to teach me how to improve and the changes in the version upgrade?
- Tomohiro Fujino asked 2 years ago
- You must login to post comments
Hi, good morning
SciChart WPF v6.6.0.26505 was just released. Can you try this version and see if you get the same error?
See what’s new here:
The stack trace you showed is related to resizing the window, the amount of data shouldn’t affect it. It’s possible that this bug fixed in 6.6 was the one you are seeing:
SC-5953 Fixed AccessViolation exception related to VRAM buffer sizes
Try it out, if you still get the problem, we are going to need more info to reproduce it. For example, a code sample that causes the problem which we can analyse.
Best regards
Andrew
- Andrew Burnett-Thompson answered 2 years ago
- You must login to post comments
Good Day.
Thank you for your reply.
The creation tool will be operated with v6.2.1.13304.
Please contact us if you have any serious bugs compared to the latest version.
- Tomohiro Fujino answered 2 years ago
-
Hi Tomohiro, there are know known bugs of AccessViolationException in the latest version of SciChart. However, our customers have varied and complex applications. If you are able to help us reproduce the problem we will be very glad to fix it. Try to isolate the problem in a small project which reproduces the issue. Send it to scichart support and our team will investigate. Best regards, Andrew
- You must login to post comments
Please login first to submit.