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
Was able to reproduce and debug on my machine a similar Exception thrown at 0x7C75E240 (VXccelEngine2D.dll) in LIDIA.exe: 0xC0000005: Access violation reading location 0x00000000 this happens with version 8.5
System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
at SciChart.Charting3D.Interop.VXccelEngine3DPINVOKE.SCRTWPFInterop_CreateRenderTarget(Int32 jarg1, Int32 jarg2)
at SciChart.Charting3D.Interop.SCRTWPFInterop.CreateRenderTarget(Int32 _iWidth, Int32 _iHeight)
at SciChart.Charting3D.Viewport3D.OnViewportResized(Int32 width, Int32 height)
at SciChart.Charting3D.SciChart3DRenderSurface.RecreateSurface()
at SciChart.Drawing.Common.RenderSurfaceBase.bwp(Object eia, SizeChangedEventArgs eib)
at System.Windows.SizeChangedEventArgs.InvokeEventHandler(Delegate genericHandler, Object genericTarget)
at System.Windows.RoutedEventArgs.InvokeHandler(Delegate handler, Object target)
at System.Windows.RoutedEventHandlerInfo.InvokeHandler(Object target, RoutedEventArgs routedEventArgs
also occurring with SciChart.Charting2D.Interop.SCRTWPFInterop
System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
at gzj.uop(HandleRef ikr, Int32 iks, Int32 ikt)
at SciChart.Charting2D.Interop.SCRTWPFInterop.CreateRenderTarget(TSRRenderingPipeline _pRenderingPipeline, Int32 _iWidth, Int32 _iHeight)
at req.mdp()
at req.mdq()
at qus.vae(ren q)
at res.BeginFrame()
at llm.RenderLoop(IRenderContext2D renderContext)
at SciChart.Charting.Visuals.SciChartSurface.DoDrawingLoop()
at SciChart.Charting.Visuals.SciChartSurface.gik()
at SciChart.Charting.Visuals.SciChartSurface.ggi(Object amh, DrawEventArgs ami)
at SciChart.Drawing.Common.RenderSurfaceBase.OnDraw()
at SciChart.Drawing.Common.RenderSurfaceBase.OnRenderTimeElapsed()
at SciChart.Drawing.Common.RenderTimer.qkc()
at SciChart.Drawing.Common.RenderTimer.qke(Object eii, Object eij)
at System.EventHandler.Invoke(Object sender, EventArgs e)
at System.Windows.Media.MediaContext.RenderMessageHandlerCore(Object resizedCompositionTarget)
at System.Windows.Media.MediaContext.RenderMessageHandler(Object resizedCompositionTarget)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)
at System.Windows.Threading.DispatcherOperation.InvokeImpl()
at System.Windows.Threading.DispatcherOperation.InvokeInSecurityContext(Object state)
Any chance to get some support to debug more deeply those issues?
- Johann Aeschlimann answered 1 month ago
- last edited 1 month ago
Hi Johann, Thanks for your inquiry. Unfortunately, the provided information is not enough to provide you with a proper solution as the mentioned exception can indicate various issues. We would appreciate if you prepare a small sample project reproducing this and share it with us for investigation or provide us with steps to reproduce this in one of the examples from the WPF examples suite. Additionally, I would recommend opening a new forums thread or submitting a priority support request here https://support.scichart.com/support/tickets/new to increase the response time. Kind regards, Lex, SciChart Technical Support Engineer
- You must login to post comments
Here is a dxdiag, I will try to create a smaller project, but as mentioned I believe it’s more link to hardware. so any info about how to configure the library to be more resilient would help.
- AC42admin LMB answered 1 month ago
- You must login to post comments
Please login first to submit.
