Problems drawing polygons in Windows 8.1

2119
11
01-25-2017 10:14 AM
ChadLeppanen
New Contributor II

Hello,

We are experiencing an issue in Windows 8.1 with the .NET Quartz release. When we attempt to add a graphic with a polygon geometry to a graphics overlay, we get a windows fatal error message box that terminates the application. We cannot catch it in any way, and logs from Event Viewer don't really give any good description.

Source code for this can be found here: GitHub - cleppanen/ArcGISRuntime-DotNet-Maptips-1: A simple demonstration of the use of "maptips" wi... 

There is a region in the MainWindow.xaml.cs where the errant code is. Also attached is the event viewer log of the application crashing.

0 Kudos
11 Replies
dotMorten_esri
Esri Frequent Contributor

Is there any chance you can get a crash dump to share? Also run "dxdiag" and export is using "save all information..." and share as well.

...also are you only experiencing this on Windows 8.1 (7 and 10 ok), or is 8.1 the only OS you tried?

0 Kudos
ChadLeppanen
New Contributor II

See attached for dxdiag output, but I was unable to find any crash dump files at this time.

Also to note, as I forgot in my initial post, the code supplied in the GitHub repo mentioned works fine in Windows 10 with no error.

0 Kudos
dotMorten_esri
Esri Frequent Contributor

The feature-levels section is empty, indicating that you don't have a hardware-enabled GPU. You need a minimum of a 9_3 level graphics card to use the runtime.

It looks like this is through remote desktop? Does the issue also occur if you're on the physical device, instead of via remote desktop?

To get the crash dump, have the VS debugger attached, and when it crashes, go to Debug -> Save Dump As.

This is a very large file though.

0 Kudos
ChadLeppanen
New Contributor II

Yes, this is a physical machine, so here’s the dxdiag taken from the physical machine itself. (My bad on that one. Forgot dxdiag would sub out the display on remote)

Yes, it does fail whether we are physically at the machine, or remoted into it.

I attached a picture of attempting to grab the dump. The error comes from the application itself, and Visual Studio is never given a chance to save the crash dump from this attempt, or my attempts in the past.

Thank you for your quick responses and your time, Morten.

Chad

0 Kudos
dotMorten_esri
Esri Frequent Contributor

You can only save the dump once VS debugging is paused, but sounds like you can't get to that state.

First try enabling native debugging (right-click project, go to project settings, select Debug tab and check on the native debugging checkbox). This might get you to a callstack.

Otherwise there's the more complex windbg tool to create crash dumps. A quick google gives you plenty of tutorials

0 Kudos
ChadLeppanen
New Contributor II

That one worked, but the crash dump, zipped even, is still over 100 MB in size. Is there somewhere else I can place this for you?

0 Kudos
PatBlair2
New Contributor II

Hello Morten and Chad.  I've uploaded Chad's crash dump to: Dropbox - CrashDump.zip 

Please let me know if you have any troubles downloading it.

0 Kudos
dotMorten_esri
Esri Frequent Contributor

Thank you. The error that's occurring internally is "Error creating depth stencil view" while rendering, which unfortunately can't be caught. That's definitely an indication that hardware capabilities aren't what the renderer is expecting (but from your dxdiag it seems you do have the minimum requirements).

Unfortunately I can't provide much workaround for you at this point, besides upgrading your GPU.

We might have to see if we can find the same or similar GPU and reproduce here, so I can unfortunately not provide you with a good immediate fix.

0 Kudos
dotMorten_esri
Esri Frequent Contributor

...btw one more thing to try: Make sure your GPU drivers are up to date: NVIDIA DRIVERS Quadro Desktop/Notebook Driver Branch 340 U14 WHQL 

0 Kudos