LightningChart Support Forums

Hi,
I'm experiencing an issue which is causing the runtime to terminate our application. We are in the process of upgrading from an earlier LightningChart version 4.2.2. We plot "live" acquisition data to the control in this case 4-12 channels. Appears the crash occurs when we change plotting modes or perform a scale change when acquisition in running. This appears to happen intermittently but frequently as it's easily re-creatable.

Thanks,


Arction.WPF.LightningChartUltimate 5.5.1.4001


Application: CardioInsight.Athena.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.ArgumentOutOfRangeException
Stack:
at System.Collections.Generic.List`1[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].RemoveAt(Int32)
at A.YG.EJ(SlimDX.Direct3D9.VertexBuffer, A.PG, Boolean, Int32 ByRef)
at Arction.WPF.LightningChartUltimate.LightningChartUltimate.PHB(Arction.WPF.LightningChartUltimate.SeriesXY.PointLineSeriesBase, Int32, Double, Double, Double, Arction.WPF.LightningChartUltimate.GraphSegmentInfo, Int32)
at Arction.WPF.LightningChartUltimate.LightningChartUltimate.OHB(System.Object)
at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
at System.Threading.ThreadPoolWorkQueue.Dispatch()

Hello,

this multithread-vertex buffer issue was fixed in LC v.6.0.1. Please update to that.

Another engineer attempted to upgrade to 6 but found the changes incompatible with our current application, as it wasn't close to being a functional system afterward. We would be more comfortable on 5.5 with a patch available to us as we are nearing the end of our development cycle and are completing our integration testing.

We have a .NET4 assemblies pack available which has the fix included.

http://www.arction.com/download/LC_v.5. ... x_net4.zip

Hi,

Thank you for the update this appears to be working well today.