KERNELBASE.dll exception occasionally thrown since upgrading to v100 from v10

23241
13
03-23-2018 02:20 AM
AaronMurphy3
New Contributor III

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.

13 Replies
MichaelBranscomb
Esri Frequent Contributor

Hi,

Can you share the reproducer?

If you cannot share here due to security/size constraints please email me on mbranscomb@esri.com.

Cheers

Mike

0 Kudos
AaronMurphy3
New Contributor III

I have found a simple way to replicate this issue. I will share my findings to your email address. For anyone else who wants a quick idea:

- create a new project

- add a tabcontrol with two tabitems

- put a map in one of the tabitems with a local tpk file used as the layer

- create a graphics layer and add a simple marker to it so it's shown on the map

- TEST TIME

- keep swapping between the two tabs really fast. It should blow up pretty quick.

BjørnarSundsbø1
Occasional Contributor II

Interesting that the recreate doesn't seem to match the initial description in the case, in regard to clicking the map. It would be great if this issue is resolved, but are you sure you recreated the initial exception you received? I had a similar exception occur and seemed to occur when clicking the map. Wasn't able to reliably reproduce this, but what I ended up reproducing was related to identify when clicking the map. While I'm not sure I submitted the original exception I experienced, but at least issue targeted. Seems I was able to recreate multiple other application crashes while I was working on another.

0 Kudos
AaronMurphy3
New Contributor III

Hi there,

Below are several of the errors from the EventViewer that were all produced by swapping between the tabs:

Faulting application name: ArcGisSample.vshost.exe, version: 12.0.30723.0, time stamp: 0x53cf4fe5

Faulting module name: RuntimeCoreNet.dll, version: 100.2.1.1962, time stamp: 0x5a823921

Exception code: 0xc0000005

Fault offset: 0x0144f577

Faulting process id: 0x3628

Faulting application start time: 0x01d3c6be7b091af9

Faulting application path: C:\Users\aaron.murphy\Documents\Visual Studio 2013\Projects\ArcGisSample\ArcGisSample\bin\Debug\ArcGisSample.vshost.exe

Faulting module path: C:\Users\aaron.murphy\Documents\Visual Studio 2013\Projects\ArcGisSample\ArcGisSample\bin\Debug\arcgisruntime100.2\client32\RuntimeCoreNet.dll

Report Id: 8dd5e0ae-13cb-4041-b9dd-1049177d222e

Faulting package full name:

Faulting package-relative application ID:

 

Faulting application name: ArcGisSample.vshost.exe, version: 12.0.30723.0, time stamp: 0x53cf4fe5

Faulting module name: igc32.dll, version: 21.20.16.4574, time stamp: 0x585d7f47

Exception code: 0xc0000005

Fault offset: 0x004ae551

Faulting process id: 0x3084

Faulting application start time: 0x01d3c6bd34a32000

Faulting application path: C:\Users\aaron.murphy\Documents\Visual Studio 2013\Projects\ArcGisSample\ArcGisSample\bin\Debug\ArcGisSample.vshost.exe

Faulting module path: C:\WINDOWS\System32\DriverStore\FileRepository\kt120137.inf_amd64_92995f20128ec2b4\igc32.dll

Report Id: 402b8830-d167-49a7-a95d-c6a7479afcfc

Faulting package full name:

Faulting package-relative application ID:

 

Faulting application name: ArcGisSample.vshost.exe, version: 12.0.30723.0, time stamp: 0x53cf4fe5

Faulting module name: ntdll.dll, version: 10.0.14393.1715, time stamp: 0x59b0d8f3

Exception code: 0xc0000005

Fault offset: 0x00048454

Faulting process id: 0x3360

Faulting application start time: 0x01d3c6bd27abfafa

Faulting application path: C:\Users\aaron.murphy\Documents\Visual Studio 2013\Projects\ArcGisSample\ArcGisSample\bin\Debug\ArcGisSample.vshost.exe

Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll

Report Id: 8749b5c5-e988-420b-8f33-f558e02ded73

Faulting package full name:

Faulting package-relative application ID:

 

Faulting application name: ArcGisSample.vshost.exe, version: 12.0.30723.0, time stamp: 0x53cf4fe5

Faulting module name: ntdll.dll, version: 10.0.14393.1715, time stamp: 0x59b0d8f3

Exception code: 0xc0000374

Fault offset: 0x000d9d71

Faulting process id: 0x2bf4

Faulting application start time: 0x01d3c6bcf3bad453

Faulting application path: C:\Users\aaron.murphy\Documents\Visual Studio 2013\Projects\ArcGisSample\ArcGisSample\bin\Debug\ArcGisSample.vshost.exe

Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll

Report Id: 3955ec59-2483-43ec-8eb3-1947ee82e940

Faulting package full name:

Faulting package-relative application ID:

 

Faulting application name: ArcGisSample.vshost.exe, version: 12.0.30723.0, time stamp: 0x53cf4fe5

Faulting module name: KERNELBASE.dll, version: 10.0.14393.2125, time stamp: 0x5a990828

Exception code: 0xe06d7363

Fault offset: 0x000daa12

Faulting process id: 0xea4

Faulting application start time: 0x01d3c6bc9a778d40

Faulting application path: C:\Users\aaron.murphy\Documents\Visual Studio 2013\Projects\ArcGisSample\ArcGisSample\bin\Debug\ArcGisSample.vshost.exe

Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll

Report Id: 1c652c41-b5ca-41c7-8c10-2a0f1ced50fc

Faulting package full name:

Faulting package-relative application ID:

0 Kudos
MichaelBranscomb
Esri Frequent Contributor

Hi Aaron,

We received the repro app via email, thanks for putting together a good simple standalone reproducer. 

We have reproduced the crash and submitted an issue in the backlog for further investigation. Many thanks for working through this with us.

As discussed on the other Geonet thread, a temporary workaround is to use the Static RenderingMode option GraphicsOverlay.

Cheers

Mike

0 Kudos
MichaelBranscomb
Esri Frequent Contributor

Hi Aaron,

In reproducing this we noted that a dedicated GPU (NVidia in this case) was much more stable compared to the Integrated Intel GPU.

Very dependent on what hardware you're deploying to, but you might be able to specify your app uses the dedicated GPU instead.

Cheers

Mike

0 Kudos
MarcoGiraldo
New Contributor II

Hi Michael.

 I am having some issue with the maps, right now and I like to do a test specifying dedicated GPU, could you tell how is it possible for a wpf project?.

Thanks.

0 Kudos
MichaelBranscomb
Esri Frequent Contributor

Hi,

Depending on the GPU configuration on the machine you're testing, you should use the Graphic Card vendor utility (e.g. NVidia Control Panel) to specify the GPU that the app uses.

Cheers

Mike

0 Kudos
AaronMurphy3
New Contributor III

After further testing I can confirm this bug was introduced in v100.2. I have tried all the recent versions and v100.1 appears to works fine.

0 Kudos