Access Violation random crashes using the runtime version 100.10

Question

Hello,

we've been having issues with our application crashing while in prolonged use (5~10 hours running) with no clear reason or pattern to allow for reliable reproducibility.

The application processes a lot of data at a time to display icons on the map as individual graphic overlays that would be rendered out on the map.

Exception information from the Event Viewer:

Application: Application.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.AccessViolationException
at RuntimeCoreNet.GeneratedWrappers.CoreSymbolLayer.CoreRT_SymbolLayer_destroy(IntPtr, IntPtr ByRef)
at RuntimeCoreNet.GeneratedWrappers.CoreWrapperBase.PrivateDestroyHandle(Boolean)
at RuntimeCoreNet.GeneratedWrappers.CoreWrapperBase.Finalize()

Faulting application name: Application.exe, version: 2.35.0.0, time stamp: 0xf224efad
Faulting module name: MSVCP140.dll, version: 14.28.29910.0, time stamp: 0x602478ba
Exception code: 0xc0000005
Fault offset: 0x0000000000012df7
Faulting process id: 0x9a4
Faulting application start time: 0x01d8dd27c3b0ed12
Faulting application path: C:\Program Files\Project\Application.exe
Faulting module path: C:\WINDOWS\SYSTEM32\MSVCP140.dll
Report Id: 052b505e-d017-439b-8df6-6a4fe6536579
Faulting package full name:
Faulting package-relative application ID:

We've been trying to recreate this but there doesn't seem to be any consistent way to reproduce this, but we think this might be related to adding symbols calls using CompositeSymbol.

We've checked to see if this issue may have been resolved, would updating the library help?

Thanks,

Lukasz.

MichaelBranscomb · Answer

You might be able to get a deeper native call stack following the instructions here: Debug using ArcGIS Runtime Windows symbol files | ArcGIS Runtime API for .NET | ArcGIS Developers

Are you able to repro on your development machines and deployment machines?

LukaszC · Answer

Hey,

we haven't yet updated to 100.15 so we do not know, and if we are to update we won't know if this would resolve the problem as we don't have a reliable way of reproducing the issue. This is why we were wondering if someone else has stumbled onto this issue already and noticed that maybe the newer release is more stable?

MichaelBranscomb · Answer

Hi,

Are you still able to repro with the current release, 100.15?

Thanks