[Application Crash] Frequent win32 exceptions in 100.2

2938
5
Jump to solution
01-10-2018 12:43 PM
BjørnarSundsbø1
Occasional Contributor II

After updating to 100.2, I experience very frequent win32 exceptions. This could either be when the application is starting (map loading), entering a Remote Desktop Connection while the application is running, or other fun situations.

The attached debugger is not able to debug this information. Are there steps you would recommend for providing you with more information about these crashes to hopefully have them quickly fixed (hot fix if possible). As it is, upgrading looks like a big risk considering the number of crashes we have experienced so far.

I've started the sample application over remote, and will see if similar issues occur there when I get back to the office tomorrow morning.

This is just a small sampling:

Faulting application name: MapTestClient.exe, version: 1.0.0.0, time stamp: 0x5a5606fe
Faulting module name: ntdll.dll, version: 10.0.15063.608, time stamp: 0x802f667e
Exception code: 0xc0000374
Fault offset: 0x000d9aba

Faulting application name: MapTestClient.exe, version: 1.0.0.0, time stamp: 0x5a5606fe
Faulting module name: RuntimeCoreNet.dll, version: 100.2.0.1912, time stamp: 0x5a31e8b2
Exception code: 0xc0000005
Fault offset: 0x0167a89c

Faulting application name: MapTestClient.exe, version: 1.0.0.0, time stamp: 0x5a5606fe
Faulting module name: ucrtbase.dll, version: 10.0.15063.674, time stamp: 0xd8c924c3
Exception code: 0xc0000409
Fault offset: 0x000a543b

Faulting application name: MapTestClient.exe, version: 1.0.0.0, time stamp: 0x5a54ea80
Faulting module name: KERNELBASE.dll, version: 10.0.15063.726, time stamp: 0x32774c02
Exception code: 0xe06d7363
Fault offset: 0x000ecbb2

Faulting application name: MapTestClient.exe, version: 1.0.0.0, time stamp: 0x5a54b608
Faulting module name: VCRUNTIME140.dll, version: 14.10.25008.0, time stamp: 0x589abc77
Exception code: 0xc0000005
Fault offset: 0x0000dc07

0 Kudos
1 Solution

Accepted Solutions
BjørnarSundsbø1
Occasional Contributor II

Issue has been fixed in internal build for 100.3

View solution in original post

0 Kudos
5 Replies
StephenHarrison2
New Contributor

I would also be interested in some assistance with how to debug these errors. We are seeing these on multiple different developer machines, running directly and through remote desktop, with no clear way to debug or get more details on the problem.

0 Kudos
MichaelBranscomb
Esri Frequent Contributor

Hi,

In order to investigate this we'll need a reproducer in the form of the simplest subset of your code that shows the problem.

In meantime, you could also:

- Enable native debugging: Go to Project Properties > Debug > Debugger engines > Enable native code debugging. 

- Get a crash dump

- Email me the location to download the file - mbranscomb@esri.com. Or alternatively I can provide an online Box folder for you to upload the zipped dump file.

Cheers

Mike

0 Kudos
GeorgeLawson
New Contributor

I am using 100.2 and I am also experiencing a very similar issue with my WPF application crashing for no apparent reason when the map is loading or just a few seconds after loading. I have put extensive logging in my application and the crash is not happening in any of my functions. Once the application fully loads, I have not seen the crash issue occur later in the application execution. It has been very painful to troubleshoot as it does not crash on every application start. The issue appears much more frequently on a few particular Windows 7 machines. On one particular Win7 machine I can usually see the crash in 1 out of 5 or 1 out of 10 starts. But, I have several Win7 that are not experiencing the issue. We launched the app over 50 times on one Win7 box with no crashes. I have seen it crash very few times on my Windows 10 development box. The one time I did, the debug dump info was not very helpful to me.

Here are a few of the logs from recent crashes:

Faulting application name: FocalPointDashboard.exe, version: 2017.0.1218.0, time stamp: 0x5ad108f8
Faulting module name: RuntimeCoreNet.dll, version: 100.2.1.1962, time stamp: 0x5a823921
Exception code: 0xc0000005
Fault offset: 0x0126ee47
Faulting process id: 0x2130
Faulting application start time: 0x01d3d3f8ae45accc
Faulting application path: C:\PoC\FocalPointDashboard\FocalPointDashboard.exe
Faulting module path: C:\PoC\FocalPointDashboard\arcgisruntime100.2\client32\RuntimeCoreNet.dll
Report Id: f7fab90c-3feb-11e8-95bc-a434d9123d69

OR

Faulting application name: FocalPointDashboard.exe, version: 2017.0.1218.0, time stamp: 0x5ad1024e
Faulting module name: ntdll.dll, version: 6.1.7601.24094, time stamp: 0x5abedfcd
Exception code: 0xc0000374
Fault offset: 0x000ce9fb
Faulting process id: 0x1a38
Faulting application start time: 0x01d3d3f220bdbcec
Faulting application path: C:\PoC\FocalPointDashboard\FocalPointDashboard.exe
Faulting module path: C:\Windows\SysWOW64\ntdll.dll
Report Id: 6793ec2c-3fe5-11e8-95bc-a434d9123d69

Faulting application name: FocalPointDashboard.exe, version: 2017.0.1218.0, time stamp: 0x5ad1024e
Faulting module name: KERNELBASE.dll, version: 6.1.7601.24094, time stamp: 0x5abee073
Exception code: 0xe06d7363
Fault offset: 0x0000c54f
Faulting process id: 0x1e20
Faulting application start time: 0x01d3d3f04567a44c
Faulting application path: C:\PoC\FocalPointDashboard\FocalPointDashboard.exe
Faulting module path: C:\Windows\syswow64\KERNELBASE.dll
Report Id: 8db9ec3c-3fe3-11e8-95bc-a434d9123d69

The crashes typically happen after the MyMapView_DrawStatusChanged event fires for the first time with a status of InProcess, then the MapView_SpatialReferenceChanged event fires but the MyMapView_DrawStatusChanged never fires again with a status of InProcess of Complete.

 

I opened a ticket with ESRI dev support on the issue. Any updates would be greatly appreciated.

Thanks,

George

0 Kudos
BjørnarSundsbø1
Occasional Contributor II

This seems to be the same as my issue. I've added trace of the events you mentioned, and this is the output:

InProgress
SpatialReference[Wkid=25832]

*crash*

You could see if you can have this issue linked with BUG-000111214 so ESRI can see if they are the same. It should be fixed for 100.3, and I am currently waiting for a fix version for this issue.

0 Kudos
BjørnarSundsbø1
Occasional Contributor II

Issue has been fixed in internal build for 100.3

0 Kudos