Hi there.
An application I work on has been using v10.2.7 of the .NET sdk for some time and never had any issues. A few weeks ago I was tasked with migrating to v100.2.1 and it appeared everything went okay. The program used to only use an ArcGISTiledLayer but I've now included another control that uses the ServiceImageTiledLayer. Since this change I have now witnessed a few occasions where my app has randomly died. The latest occurrence of this was this morning where I ran up my application and left it for 5 minutes (barely touching the map controls), then when I came back and clicked on the control containing the ServiceImageTiledLayer it instantly threw up an exception.. and I mean one of the big bad ones that I can't prevent and handle. I presume this is happening in the C++ of the .NET sdk. I have managed to get the log information from event viewer:
Faulting application name: Main.exe, version: 0.0.0.0, time stamp: 0x5ab3d519
Faulting module name: KERNELBASE.dll, version: 10.0.14393.1770, time stamp: 0x59bf2bcf
Exception code: 0xe06d7363
Fault offset: 0x000daa12
Faulting process id: 0x3228
Faulting application start time: 0x01d3c282c5892d47
Faulting application path: C:\RDRIVE\Development\Main.exe
Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
Report Id: 4d5dc301-ba78-4df2-9d30-1def5e0c9573
Faulting package full name:
Faulting package-relative application ID:
This has only been happening since the upgrade to v100 and whenever it happens it is ALWAYS been caused by me clicking the map. I accept that I could be doing something wrong, but given the nature of the exception and the little amount I actually use of the .NET SDK I can't help but feel like this is an internal problem.
