locked
Application dies unexpectedly RRS feed

  • Question

  • OK, so this is a tricky one.

    I have been developing a Windows 8 Store app for a while, it has been in the store as well. Now, suddenly, the app just dies after loading some data from a JSON call. There is no exception, no unhandled exception to handle - nothing. Pouf! Dead.

    How do I get about figuring out why it dies? It seems like one of the good old memory/pointer errors...but without any help from VS 2012, I dont know where to start looking.

    Monday, September 24, 2012 4:34 PM

Answers

  • Seeing vrfcore!VerifierStopMessageEx indicates you have AppVerifier turned on.  The error on shutdown is likely something you can read in the AppVerifier logs under  %ALLUSERSPROFILE%\AppVerifierLog.

    Since AppVerifier can also be used to simulate low-memory conditions, you might want to check whether this got left on using the AppVerif UI.  (Make sure "Low Resource Simulation" is not set for your app.

    Hope this helps,
    Matt


    XAML SDET Lead : Input / DirectManipulation / Accessibility

    • Marked as answer by FalafelSoftware Wednesday, September 26, 2012 12:20 AM
    Tuesday, September 25, 2012 7:28 PM

All replies

  • Odds are the JSON call is resulting in a native exception that is not getting caught due to debugging settings.  Here's a couple ideas.  If they don't work, a Live drive copy of a repro app is the easiest way for me to help you.

    1) Enable mixed mode debugging for your app (Project Properties, Debug, "Debugger Type", set to Mixed) and turn off "Just my code" (tools/options/debugging), turn on all first-chance exceptions, then repro the problem.  Odds are you will catch it this time.

    2) Install WinDBG,  (http://msdn.microsoft.com/en-us/windows/hardware/gg463009.aspx)  run Windbg -I to register it as the JIT debugger, repro your problem.  If this catches it, you can get a stack with kp, or just try auto analysis with !analyze -v, or .dump -mfh <File path> to make a dump you can share here on the forum.

    Hope this helps,
    Matt


    XAML SDET Lead : Input / DirectManipulation / Accessibility

    Monday, September 24, 2012 5:24 PM
  • Thanks for the response. I will try some of these techniques. Notable is that the app doesn't die immediately during the JSON parsing, it dies like 10 seconds later... And if I load fewer objects in the result set, it doesn't die.
    Monday, September 24, 2012 6:03 PM
  • Stack would be super helpful here, but do you happen to be putting these elements into a custom control which derives from ListView / GridView?

    XAML SDET Lead : Input / DirectManipulation / Accessibility

    Monday, September 24, 2012 6:13 PM
  • With mixed mode, the app doesn't start. The splash screen comes up and that is it. It doesn't even show up in the list of processes. When I kill the app with F4, an error message show up "Unable to activate Windows Store app....the activation request failed with error "the app didn't start".

    Monday, September 24, 2012 8:21 PM
  • The WinDbg approach is equally unsuccessful.

    Dumping fails:

    0:000>  .dump -mfh "d:\dumps\EB1.dmp"
    Creating d:\dumps\EB1.dmp - mini user dump
    GetContextState failed, 0x80070057
    Unable to get event thread context, Win32 error 0n87
    GenGetProcessInfo.Start(0x698) failed, 0x8007012b
    Dump creation failed, Win32 error 0n299
        "Only part of a ReadProcessMemory or WriteProcessMemory request was completed."
    GetContextState failed, 0x80070057
    GetContextState failed, 0x80070057
    GetContextState failed, 0x80070057

    Analyze fails to, and I see this

    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    *                                                                   *
    * The Symbol Path can be set by:                                    *
    *   using the _NT_SYMBOL_PATH environment variable.                 *
    *   using the -y <symbol_path> argument when starting the debugger. *
    *   using .sympath and .sympath+                                    *
    *********************************************************************

    I don't know what to make of all this...


    Microsoft (R) Windows Debugger Version 6.2.9200.16384 X86
    Copyright (c) Microsoft Corporation. All rights reserved.

    *** wait with pending attach
    Symbol search path is: *** Invalid ***
    ****************************************************************************
    * Symbol loading may be unreliable without a symbol search path.           *
    * Use .symfix to have the debugger choose a symbol path.                   *
    * After setting your symbol path, use .reload to refresh symbol locations. *
    ****************************************************************************
    Executable search path is:
    ModLoad: 00eb0000 00eea000   D:\Source\SVCCViewer\WP7CCViewer\EventBoard.W8\bin\Debug\AppX\EventBoard.W8.exe
    ModLoad: 778d0000 77a27000   C:\WINDOWS\SYSTEM32\ntdll.dll
    ModLoad: 6d4c0000 6d529000   C:\WINDOWS\syswow64\verifier.dll
    ModLoad: 71c10000 71c3f000   C:\WINDOWS\SYSTEM32\vrfcore.dll
    ModLoad: 6b450000 6b4a9000   C:\WINDOWS\SYSTEM32\vfbasics.dll
    ModLoad: 71940000 71953000   C:\WINDOWS\SYSTEM32\vfnet.dll
    ModLoad: 76800000 76930000   C:\WINDOWS\SYSTEM32\KERNEL32.dll
    ModLoad: 74fd0000 75076000   C:\WINDOWS\SYSTEM32\KERNELBASE.dll
    ModLoad: 718e0000 718f7000   C:\WINDOWS\SYSTEM32\vfnws.dll
    ModLoad: 6eda0000 6edea000   C:\WINDOWS\SYSTEM32\MSCOREE.DLL
    ModLoad: 77320000 773ce000   C:\WINDOWS\SYSTEM32\ADVAPI32.dll
    ModLoad: 77210000 772c1000   C:\WINDOWS\SYSTEM32\msvcrt.dll
    ModLoad: 76930000 76964000   C:\WINDOWS\SYSTEM32\sechost.dll
    ModLoad: 775a0000 7764c000   C:\WINDOWS\SYSTEM32\RPCRT4.dll
    ModLoad: 74f50000 74f6c000   C:\WINDOWS\SYSTEM32\SspiCli.dll
    ModLoad: 74f40000 74f49000   C:\WINDOWS\SYSTEM32\CRYPTBASE.dll
    ModLoad: 74ee0000 74f31000   C:\WINDOWS\SYSTEM32\bcryptPrimitives.dll
    ModLoad: 6ed20000 6ed9a000   C:\Windows\Microsoft.NET\Framework\v4.0.30319\mscoreei.dll
    ModLoad: 771c0000 77200000   C:\WINDOWS\SYSTEM32\SHLWAPI.dll
    ModLoad: 753d0000 754e6000   C:\WINDOWS\SYSTEM32\USER32.dll
    ModLoad: 751f0000 752ed000   C:\WINDOWS\SYSTEM32\GDI32.dll
    ModLoad: 75380000 753a0000   C:\WINDOWS\system32\IMM32.DLL
    ModLoad: 76ec0000 76f9c000   C:\WINDOWS\SYSTEM32\MSCTF.dll
    ModLoad: 61a10000 620a2000   C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll
    ModLoad: 6b5f0000 6b6c3000   C:\WINDOWS\SYSTEM32\MSVCR110_CLR0400.dll
    ModLoad: 776d0000 77806000   C:\WINDOWS\SYSTEM32\combase.dll
    ModLoad: 754f0000 75609000   C:\WINDOWS\SYSTEM32\ole32.dll
    ModLoad: 5ba60000 5ca1f000   C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\mscorlib\51e2934144ba15628ba5a31be2dae7dc\mscorlib.ni.dll
    ModLoad: 71d70000 71d78000   C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\System.Runtime\0e4ddbdd302ec7687a079b137bc2258d\System.Runtime.ni.dll
    ModLoad: 0fb40000 0fbc1000   C:\Windows\System32\twinapi.dll
    ModLoad: 0ffe0000 10056000   C:\Windows\System32\WinTypes.dll
    ModLoad: 61460000 614ce000   C:\Windows\Microsoft.NET\Framework\v4.0.30319\clrjit.dll
    ModLoad: 64400000 646bd000   C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\Windows.UI.Xaml\0e03623a072f7c98745c3a47718d1ce5\Windows.UI.Xaml.ni.dll
    ModLoad: 71d40000 71d45000   C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\System.Runtbff93e24#\48892bf037b90424bc29284bf25f9953\System.Runtime.InteropServices.WindowsRuntime.ni.dll
    ModLoad: 0de80000 0e8d2000   C:\Windows\System32\Windows.UI.Xaml.dll
    ModLoad: 6d8e0000 6d91d000   C:\WINDOWS\SYSTEM32\NInput.dll
    ModLoad: 75610000 766d5000   C:\WINDOWS\SYSTEM32\SHELL32.dll
    ModLoad: 77130000 771bb000   C:\WINDOWS\SYSTEM32\OLEAUT32.dll
    ModLoad: 76970000 76b29000   C:\WINDOWS\SYSTEM32\WININET.dll
    ModLoad: 62e60000 63003000   C:\WINDOWS\SYSTEM32\d3d11.dll
    ModLoad: 70260000 70279000   C:\WINDOWS\SYSTEM32\dwmapi.dll
    ModLoad: 706e0000 70768000   C:\WINDOWS\SYSTEM32\UxTheme.dll
    ModLoad: 766e0000 767fe000   C:\WINDOWS\SYSTEM32\urlmon.dll
    ModLoad: 5cdb0000 5ce8f000   C:\WINDOWS\SYSTEM32\UIAutomationCore.DLL
    ModLoad: 76b50000 76ceb000   C:\WINDOWS\SYSTEM32\iertutil.dll
    ModLoad: 6fed0000 6ff2c000   C:\WINDOWS\SYSTEM32\dxgi.dll
    ModLoad: 749d0000 74a45000   C:\WINDOWS\SYSTEM32\shcore.dll
    ModLoad: 73750000 7376a000   C:\WINDOWS\SYSTEM32\CRYPTSP.dll
    ModLoad: 736d0000 7370e000   C:\WINDOWS\system32\rsaenh.dll
    ModLoad: 5edf0000 5eeac000   C:\Windows\SYSTEM32\actxprxy.dll
    ModLoad: 6b320000 6b446000   C:\Windows\SYSTEM32\Windows.UI.Immersive.dll
    ModLoad: 5eeb0000 5f00c000   C:\WINDOWS\SYSTEM32\DUI70.dll
    ModLoad: 63080000 631df000   C:\WINDOWS\SYSTEM32\dwrite.dll
    ModLoad: 6ff30000 70257000   C:\WINDOWS\SYSTEM32\d2d1.dll
    ModLoad: 71f40000 71f59000   C:\WINDOWS\SYSTEM32\DXGIDebug.dll
    ModLoad: 62c60000 62e55000   C:\WINDOWS\SYSTEM32\D3D10Warp.dll
    ModLoad: 620b0000 62c57000   C:\WINDOWS\SYSTEM32\nvwgf2um.dll
    ModLoad: 74540000 74548000   C:\WINDOWS\SYSTEM32\VERSION.dll
    ModLoad: 6b1a0000 6b244000   C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\Windows.App640a3541#\8417f3ad31c62b2d7d4395095e66ec87\Windows.ApplicationModel.ni.dll
    ModLoad: 71c00000 71c05000   C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\System.IO\374c1635be4cd3cf2b17635c142768aa\System.IO.ni.dll
    ModLoad: 71930000 71935000   C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\System.Thre7bb2aad0#\0ac2aaf22a48c910cb33f22c7c3ca060\System.Threading.Tasks.ni.dll
    ModLoad: 63f50000 63ffc000   C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\Windows.Storage\f6c38a127b6d3a90b9000ec1cef08c7e\Windows.Storage.ni.dll
    ModLoad: 718a0000 718a5000   C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\System.Collections\058cde361faa0dfb79233c0f50d947a7\System.Collections.ni.dll
    ModLoad: 6b2b0000 6b31a000   C:\Windows\SYSTEM32\MrmCoreR.dll
    ModLoad: 5f7b0000 5f7ff000   C:\WINDOWS\SYSTEM32\Bcp47Langs.dll
    ModLoad: 749b0000 749c1000   C:\WINDOWS\SYSTEM32\profapi.dll
    ModLoad: 721a0000 721ba000   C:\WINDOWS\SYSTEM32\bcrypt.dll
    ModLoad: 63e90000 63f4e000   C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\Windows.UI\3f8eec47d1ecac7ff220c3971fd9a669\Windows.UI.ni.dll
    ModLoad: 71890000 71895000   C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\System.ObjectModel\01dfdf5eeaf917d38d43889d6489a9c5\System.ObjectModel.ni.dll
    ModLoad: 5d8e0000 5e259000   C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\System\e40da7a49f8c3f0108e7c835b342f382\System.ni.dll
    ModLoad: 64840000 648ca000   C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\System.Runt0d283adf#\b7afb40d6e4a7dd9a584749d6fe8fdb3\System.Runtime.WindowsRuntime.ni.dll
    ModLoad: 702c0000 702f0000   C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\Windows.Foundation\e269aef156b52ff27f4d2f1c062f4f66\Windows.Foundation.ni.dll
    ModLoad: 71870000 71875000   C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\System.Threading\0eff4e5e75940f0bceb67aa5a7809f59\System.Threading.ni.dll
    ModLoad: 71850000 7185e000   C:\Windows\System32\Windows.ApplicationModel.dll
    ModLoad: 6e660000 6e69b000   C:\WINDOWS\SYSTEM32\windows.ui.dll
    ModLoad: 68f70000 68f93000   C:\WINDOWS\SYSTEM32\dcomp.dll
    ModLoad: 70780000 70785000   C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\System.Linq\8f94a5820f489d7a30d757fd210e8ba8\System.Linq.ni.dll
    ModLoad: 5b0d0000 5b77e000   C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\System.Core\b9f7adbc90a2bcbe8eb9e6e8d2bb975b\System.Core.ni.dll
    ModLoad: 6f6c0000 6f6dc000   C:\Windows\System32\biwinrt.dll
    ModLoad: 6db00000 6db39000   C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\Windows.Data\46126670a417e0e9977f04e116d7e7f8\Windows.Data.ni.dll
    ModLoad: 6f3c0000 6f3e3000   C:\Windows\System32\Windows.Storage.ApplicationData.dll
    ModLoad: 5cb00000 5cc19000   C:\WINDOWS\SYSTEM32\PROPSYS.dll
    ModLoad: 5f3c0000 5f66b000   C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\System.Runteb92aa12#\293cfe2c05a8ee921726927fd00ea81c\System.Runtime.Serialization.ni.dll
    ModLoad: 6ee40000 6ee45000   C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\System.Diagaa8d7fa5#\193fa35f2f1db384e6a7406583d8dc60\System.Diagnostics.Debug.ni.dll
    ModLoad: 6b9f0000 6ba11000   C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\SMDiagnostics\98e3281d79512c9a2a0a89e3bc2e554f\SMDiagnostics.ni.dll
    ModLoad: 5a4f0000 5ac28000   C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\System.Xml\9ba07396ae369d010c5c3927a82ef426\System.Xml.ni.dll
    ModLoad: 63dc0000 63e87000   C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\System.Servd1dec626#\df55f04bc0ebe6c1abde4bc467bf4d03\System.ServiceModel.Internals.ni.dll
    ModLoad: 5f6c0000 5f7ab000   C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\System.Configuration\28586400bcaf94c13a9fd0dff4a1e090\System.Configuration.ni.dll
    ModLoad: 60100000 6032a000   C:\WINDOWS\SYSTEM32\msftedit.dll
    ModLoad: 6aa20000 6aab7000   C:\Windows\System32\Windows.Globalization.dll
    ModLoad: 5ce90000 5cfd6000   C:\WINDOWS\system32\windowscodecs.dll
    ModLoad: 5ca40000 5ca87000   C:\WINDOWS\SYSTEM32\msv1_0.DLL
    ModLoad: 5ca20000 5ca32000   C:\WINDOWS\SYSTEM32\cryptdll.dll
    ModLoad: 43c50000 43c75000   C:\WINDOWS\SYSTEM32\logoncli.dll
    ModLoad: 6ee30000 6ee35000   C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\System.Runt1e58aa76#\112858dd9e1beae179649280fdb1d80e\System.Runtime.Extensions.ni.dll
    ModLoad: 6ab10000 6ab45000   C:\Windows\System32\Windows.Networking.Connectivity.dll
    ModLoad: 6ee20000 6ee25000   C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\System.Net.Requests\942a9b1970d558dc2d2af20945e9171a\System.Net.Requests.ni.dll
    ModLoad: 74c20000 74c74000   C:\WINDOWS\SYSTEM32\rasapi32.dll
    ModLoad: 74c00000 74c16000   C:\WINDOWS\SYSTEM32\rasman.dll
    ModLoad: 77670000 776c0000   C:\WINDOWS\SYSTEM32\WS2_32.dll
    ModLoad: 76e00000 76e08000   C:\WINDOWS\SYSTEM32\NSI.dll
    ModLoad: 74a50000 74a9a000   C:\WINDOWS\system32\mswsock.dll
    ModLoad: 73050000 730d3000   C:\WINDOWS\SYSTEM32\winhttp.dll
    ModLoad: 74bd0000 74bf2000   C:\WINDOWS\SYSTEM32\IPHLPAPI.DLL
    ModLoad: 747e0000 747e8000   C:\WINDOWS\SYSTEM32\WINNSI.DLL
    ModLoad: 747d0000 747e0000   C:\WINDOWS\SYSTEM32\dhcpcsvc6.DLL
    ModLoad: 747b0000 747c2000   C:\WINDOWS\SYSTEM32\dhcpcsvc.DLL
    ModLoad: 72590000 72605000   C:\WINDOWS\SYSTEM32\DNSAPI.dll
    ModLoad: 73740000 73747000   C:\Windows\System32\rasadhlp.dll
    ModLoad: 74770000 747af000   C:\WINDOWS\System32\fwpuclnt.dll
    ModLoad: 3f8c0000 3f8c9000   C:\WINDOWS\SYSTEM32\secur32.dll
    ModLoad: 6f630000 6f684000   C:\WINDOWS\SYSTEM32\schannel.dll
    ModLoad: 7e730000 7e8b8000   C:\WINDOWS\SYSTEM32\CRYPT32.dll
    ModLoad: 753b0000 753c2000   C:\WINDOWS\SYSTEM32\MSASN1.dll
    ModLoad: 3b4c0000 3b4d9000   C:\WINDOWS\SYSTEM32\ncrypt.dll
    ModLoad: 72170000 72197000   C:\WINDOWS\SYSTEM32\NTASN1.dll
    ModLoad: 5ba40000 5ba55000   C:\WINDOWS\system32\ncryptsslp.dll
    ModLoad: 5b0b0000 5b0cd000   C:\WINDOWS\SYSTEM32\gpapi.dll
    ModLoad: 5f390000 5f3c0000   C:\WINDOWS\System32\wpnapps.dll
    Break-in sent, waiting 30 seconds...
    WARNING: Break-in timed out, suspending.
             This is usually caused by another thread holding the loader lock
    (698.1314): Wake debugger - code 80000007 (first chance)
    *** ERROR: Symbol file could not be found.  Defaulted to export symbols for C:\WINDOWS\SYSTEM32\ntdll.dll -
    *** ERROR: Symbol file could not be found.  Defaulted to export symbols for C:\WINDOWS\SYSTEM32\KERNELBASE.dll -
    eax=00000000 ebx=00000002 ecx=00000000 edx=00000000 esi=0106ef2c edi=0106efec
    eip=77911318 esp=0106ede0 ebp=0106ee00 iopl=0         nv up ei pl nz ac po nc
    cs=0023  ss=002b  ds=002b  es=002b  fs=0053  gs=002b             efl=00000212
    ntdll!ZwWaitForMultipleObjects+0xc:
    77911318 c21400          ret     14h
    0:000> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Exception Analysis                                   *
    *                                                                             *
    *******************************************************************************

    ***** OS symbols are WRONG. Please fix symbols to do analysis.

    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Either you specified an unqualified symbol, or your debugger   ***
    ***    doesn't have full symbol information.  Unqualified symbol      ***
    ***    resolution is turned off by default. Please either specify a   ***
    ***    fully qualified symbol module!symbolname, or enable resolution ***
    ***    of unqualified symbols by typing ".symopt- 100". Note that   ***
    ***    enabling unqualified symbol resolution with network symbol     ***
    ***    server shares in the symbol path may cause the debugger to     ***
    ***    appear to hang for long periods of time when an incorrect      ***
    ***    symbol name is typed or the network symbol server is down.     ***
    ***                                                                   ***
    ***    For some commands to work properly, your symbol path           ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: ntdll!_PEB                                    ***
    ***                                                                   ***
    *************************************************************************
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    *                                                                   *
    * The Symbol Path can be set by:                                    *
    *   using the _NT_SYMBOL_PATH environment variable.                 *
    *   using the -y <symbol_path> argument when starting the debugger. *
    *   using .sympath and .sympath+                                    *
    *********************************************************************
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    *                                                                   *
    * The Symbol Path can be set by:                                    *
    *   using the _NT_SYMBOL_PATH environment variable.                 *
    *   using the -y <symbol_path> argument when starting the debugger. *
    *   using .sympath and .sympath+                                    *
    *********************************************************************
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    *                                                                   *
    * The Symbol Path can be set by:                                    *
    *   using the _NT_SYMBOL_PATH environment variable.                 *
    *   using the -y <symbol_path> argument when starting the debugger. *
    *   using .sympath and .sympath+                                    *
    *********************************************************************
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    *                                                                   *
    * The Symbol Path can be set by:                                    *
    *   using the _NT_SYMBOL_PATH environment variable.                 *
    *   using the -y <symbol_path> argument when starting the debugger. *
    *   using .sympath and .sympath+                                    *
    *********************************************************************
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    *                                                                   *
    * The Symbol Path can be set by:                                    *
    *   using the _NT_SYMBOL_PATH environment variable.                 *
    *   using the -y <symbol_path> argument when starting the debugger. *
    *   using .sympath and .sympath+                                    *
    *********************************************************************
    GetContextState failed, 0x80070057
    GetContextState failed, 0x80070057
    GetContextState failed, 0x80070057
    Unable to get program counter
    GetContextState failed, 0x80070057
    GetContextState failed, 0x80070057
    GetContextState failed, 0x80070057
    Unable to get program counter
    GetContextState failed, 0x80070057
    GetContextState failed, 0x80070057
    GetContextState failed, 0x80070057
    Unable to get program counter
    GetContextState failed, 0x80070057
    GetContextState failed, 0x80070057
    GetContextState failed, 0x80070057
    Unable to get program counter
    GetContextState failed, 0x80070057
    GetContextState failed, 0x80070057
    GetContextState failed, 0x80070057
    Unable to get program counter
    GetContextState failed, 0x80070057
    GetContextState failed, 0x80070057
    GetContextState failed, 0x80070057
    Unable to get program counter
    GetContextState failed, 0x80070057
    GetContextState failed, 0x80070057
    GetContextState failed, 0x80070057
    Unable to get program counter
    GetContextState failed, 0x80070057
    GetContextState failed, 0x80070057
    GetContextState failed, 0x80070057
    Unable to get program counter
    GetContextState failed, 0x80070057
    GetContextState failed, 0x80070057
    GetContextState failed, 0x80070057
    Unable to get program counter
    GetContextState failed, 0x80070057

    Monday, September 24, 2012 8:50 PM
  • Here are some more attempts


    Microsoft (R) Windows Debugger Version 6.2.9200.16384 X86
    Copyright (c) Microsoft Corporation. All rights reserved.

    *** wait with pending attach
    Symbol search path is: *** Invalid ***
    ****************************************************************************
    * Symbol loading may be unreliable without a symbol search path.           *
    * Use .symfix to have the debugger choose a symbol path.                   *
    * After setting your symbol path, use .reload to refresh symbol locations. *
    ****************************************************************************
    Executable search path is:
    ModLoad: 00c00000 00c3a000   D:\Source\SVCCViewer\WP7CCViewer\EventBoard.W8\bin\Debug\AppX\EventBoard.W8.exe
    ModLoad: 778d0000 77a27000   C:\WINDOWS\SYSTEM32\ntdll.dll
    ModLoad: 6d4c0000 6d529000   C:\WINDOWS\syswow64\verifier.dll
    ModLoad: 71930000 7195f000   C:\WINDOWS\SYSTEM32\vrfcore.dll
    ModLoad: 6bf60000 6bfb9000   C:\WINDOWS\SYSTEM32\vfbasics.dll
    ModLoad: 718e0000 718f3000   C:\WINDOWS\SYSTEM32\vfnet.dll
    ModLoad: 76800000 76930000   C:\WINDOWS\SYSTEM32\KERNEL32.dll
    ModLoad: 74fd0000 75076000   C:\WINDOWS\SYSTEM32\KERNELBASE.dll
    ModLoad: 71890000 718a7000   C:\WINDOWS\SYSTEM32\vfnws.dll
    ModLoad: 6eda0000 6edea000   C:\WINDOWS\SYSTEM32\MSCOREE.DLL
    ModLoad: 77320000 773ce000   C:\WINDOWS\SYSTEM32\ADVAPI32.dll
    ModLoad: 77210000 772c1000   C:\WINDOWS\SYSTEM32\msvcrt.dll
    ModLoad: 76930000 76964000   C:\WINDOWS\SYSTEM32\sechost.dll
    ModLoad: 775a0000 7764c000   C:\WINDOWS\SYSTEM32\RPCRT4.dll
    ModLoad: 74f50000 74f6c000   C:\WINDOWS\SYSTEM32\SspiCli.dll
    ModLoad: 74f40000 74f49000   C:\WINDOWS\SYSTEM32\CRYPTBASE.dll
    ModLoad: 74ee0000 74f31000   C:\WINDOWS\SYSTEM32\bcryptPrimitives.dll
    ModLoad: 6ed20000 6ed9a000   C:\Windows\Microsoft.NET\Framework\v4.0.30319\mscoreei.dll
    ModLoad: 771c0000 77200000   C:\WINDOWS\SYSTEM32\SHLWAPI.dll
    ModLoad: 753d0000 754e6000   C:\WINDOWS\SYSTEM32\USER32.dll
    ModLoad: 751f0000 752ed000   C:\WINDOWS\SYSTEM32\GDI32.dll
    ModLoad: 75380000 753a0000   C:\WINDOWS\system32\IMM32.DLL
    ModLoad: 76ec0000 76f9c000   C:\WINDOWS\SYSTEM32\MSCTF.dll
    ModLoad: 61a10000 620a2000   C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll
    ModLoad: 6b5f0000 6b6c3000   C:\WINDOWS\SYSTEM32\MSVCR110_CLR0400.dll
    ModLoad: 776d0000 77806000   C:\WINDOWS\SYSTEM32\combase.dll
    ModLoad: 754f0000 75609000   C:\WINDOWS\SYSTEM32\ole32.dll
    ModLoad: 5ba60000 5ca1f000   C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\mscorlib\51e2934144ba15628ba5a31be2dae7dc\mscorlib.ni.dll
    ModLoad: 71d70000 71d78000   C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\System.Runtime\0e4ddbdd302ec7687a079b137bc2258d\System.Runtime.ni.dll
    ModLoad: 0fb40000 0fbc1000   C:\Windows\System32\twinapi.dll
    ModLoad: 0ffe0000 10056000   C:\Windows\System32\WinTypes.dll
    ModLoad: 61460000 614ce000   C:\Windows\Microsoft.NET\Framework\v4.0.30319\clrjit.dll
    ModLoad: 64400000 646bd000   C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\Windows.UI.Xaml\0e03623a072f7c98745c3a47718d1ce5\Windows.UI.Xaml.ni.dll
    ModLoad: 71d40000 71d45000   C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\System.Runtbff93e24#\48892bf037b90424bc29284bf25f9953\System.Runtime.InteropServices.WindowsRuntime.ni.dll
    ModLoad: 0dd60000 0e7b2000   C:\Windows\System32\Windows.UI.Xaml.dll
    ModLoad: 6d8e0000 6d91d000   C:\WINDOWS\SYSTEM32\NInput.dll
    ModLoad: 75610000 766d5000   C:\WINDOWS\SYSTEM32\SHELL32.dll
    ModLoad: 77130000 771bb000   C:\WINDOWS\SYSTEM32\OLEAUT32.dll
    ModLoad: 76970000 76b29000   C:\WINDOWS\SYSTEM32\WININET.dll
    ModLoad: 62e60000 63003000   C:\WINDOWS\SYSTEM32\d3d11.dll
    ModLoad: 70260000 70279000   C:\WINDOWS\SYSTEM32\dwmapi.dll
    ModLoad: 706e0000 70768000   C:\WINDOWS\SYSTEM32\UxTheme.dll
    ModLoad: 766e0000 767fe000   C:\WINDOWS\SYSTEM32\urlmon.dll
    ModLoad: 5cdb0000 5ce8f000   C:\WINDOWS\SYSTEM32\UIAutomationCore.DLL
    ModLoad: 76b50000 76ceb000   C:\WINDOWS\SYSTEM32\iertutil.dll
    ModLoad: 6fed0000 6ff2c000   C:\WINDOWS\SYSTEM32\dxgi.dll
    ModLoad: 749d0000 74a45000   C:\WINDOWS\SYSTEM32\shcore.dll
    ModLoad: 73750000 7376a000   C:\WINDOWS\SYSTEM32\CRYPTSP.dll
    ModLoad: 736d0000 7370e000   C:\WINDOWS\system32\rsaenh.dll
    ModLoad: 5edf0000 5eeac000   C:\Windows\SYSTEM32\actxprxy.dll
    ModLoad: 6b380000 6b4a6000   C:\Windows\SYSTEM32\Windows.UI.Immersive.dll
    ModLoad: 5eeb0000 5f00c000   C:\WINDOWS\SYSTEM32\DUI70.dll
    ModLoad: 63080000 631df000   C:\WINDOWS\SYSTEM32\dwrite.dll
    ModLoad: 6ff30000 70257000   C:\WINDOWS\SYSTEM32\d2d1.dll
    ModLoad: 71f40000 71f59000   C:\WINDOWS\SYSTEM32\DXGIDebug.dll
    ModLoad: 62c60000 62e55000   C:\WINDOWS\SYSTEM32\D3D10Warp.dll
    ModLoad: 620b0000 62c57000   C:\WINDOWS\SYSTEM32\nvwgf2um.dll
    ModLoad: 74540000 74548000   C:\WINDOWS\SYSTEM32\VERSION.dll
    ModLoad: 6b1a0000 6b244000   C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\Windows.App640a3541#\8417f3ad31c62b2d7d4395095e66ec87\Windows.ApplicationModel.ni.dll
    ModLoad: 71c10000 71c15000   C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\System.IO\374c1635be4cd3cf2b17635c142768aa\System.IO.ni.dll
    ModLoad: 71870000 71875000   C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\System.Thre7bb2aad0#\0ac2aaf22a48c910cb33f22c7c3ca060\System.Threading.Tasks.ni.dll
    ModLoad: 63f50000 63ffc000   C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\Windows.Storage\f6c38a127b6d3a90b9000ec1cef08c7e\Windows.Storage.ni.dll
    ModLoad: 71850000 71855000   C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\System.Collections\058cde361faa0dfb79233c0f50d947a7\System.Collections.ni.dll
    ModLoad: 6b130000 6b19a000   C:\Windows\SYSTEM32\MrmCoreR.dll
    ModLoad: 5f7b0000 5f7ff000   C:\WINDOWS\SYSTEM32\Bcp47Langs.dll
    ModLoad: 749b0000 749c1000   C:\WINDOWS\SYSTEM32\profapi.dll
    ModLoad: 721a0000 721ba000   C:\WINDOWS\SYSTEM32\bcrypt.dll
    ModLoad: 63e90000 63f4e000   C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\Windows.UI\3f8eec47d1ecac7ff220c3971fd9a669\Windows.UI.ni.dll
    ModLoad: 70780000 70785000   C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\System.ObjectModel\01dfdf5eeaf917d38d43889d6489a9c5\System.ObjectModel.ni.dll
    ModLoad: 5d8e0000 5e259000   C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\System\e40da7a49f8c3f0108e7c835b342f382\System.ni.dll
    ModLoad: 64840000 648ca000   C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\System.Runt0d283adf#\b7afb40d6e4a7dd9a584749d6fe8fdb3\System.Runtime.WindowsRuntime.ni.dll
    ModLoad: 702c0000 702f0000   C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\Windows.Foundation\e269aef156b52ff27f4d2f1c062f4f66\Windows.Foundation.ni.dll
    ModLoad: 6f3e0000 6f3e5000   C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\System.Threading\0eff4e5e75940f0bceb67aa5a7809f59\System.Threading.ni.dll
    ModLoad: 6f3d0000 6f3de000   C:\Windows\System32\Windows.ApplicationModel.dll
    ModLoad: 6db00000 6db3b000   C:\WINDOWS\SYSTEM32\windows.ui.dll
    ModLoad: 68f70000 68f93000   C:\WINDOWS\SYSTEM32\dcomp.dll
    ModLoad: 6f3c0000 6f3c5000   C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\System.Linq\8f94a5820f489d7a30d757fd210e8ba8\System.Linq.ni.dll
    ModLoad: 5b0d0000 5b77e000   C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\System.Core\b9f7adbc90a2bcbe8eb9e6e8d2bb975b\System.Core.ni.dll
    ModLoad: 6ee30000 6ee4c000   C:\Windows\System32\biwinrt.dll
    ModLoad: 6ee20000 6ee29000   C:\Windows\System32\Windows.ApplicationModel.Background.TimeBroker.dll
    ModLoad: 6e6d0000 6e6d7000   C:\WINDOWS\SYSTEM32\TimeBrokerClient.dll
    ModLoad: 6e650000 6e65a000   C:\Windows\System32\Windows.ApplicationModel.Background.SystemEventsBroker.dll
    ModLoad: 6dc70000 6dc77000   C:\WINDOWS\SYSTEM32\SystemEventsBrokerClient.dll
    ModLoad: 6d5c0000 6d5e3000   C:\Windows\System32\Windows.Storage.ApplicationData.dll
    ModLoad: 5cb00000 5cc19000   C:\WINDOWS\SYSTEM32\PROPSYS.dll
    ModLoad: 60100000 6032a000   C:\WINDOWS\SYSTEM32\msftedit.dll
    ModLoad: 6aa20000 6aab7000   C:\Windows\System32\Windows.Globalization.dll
    ModLoad: 5f3c0000 5f66b000   C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\System.Runteb92aa12#\293cfe2c05a8ee921726927fd00ea81c\System.Runtime.Serialization.ni.dll
    ModLoad: 6dc60000 6dc65000   C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\System.Diagaa8d7fa5#\193fa35f2f1db384e6a7406583d8dc60\System.Diagnostics.Debug.ni.dll
    ModLoad: 6ce10000 6ce31000   C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\SMDiagnostics\98e3281d79512c9a2a0a89e3bc2e554f\SMDiagnostics.ni.dll
    ModLoad: 5f6c0000 5f7ab000   C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\System.Configuration\28586400bcaf94c13a9fd0dff4a1e090\System.Configuration.ni.dll
    ModLoad: 5a4f0000 5ac28000   C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\System.Xml\9ba07396ae369d010c5c3927a82ef426\System.Xml.ni.dll
    ModLoad: 6b9e0000 6ba15000   C:\Windows\System32\Windows.Networking.Connectivity.dll
    ModLoad: 6d920000 6d925000   C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\System.Net.Requests\942a9b1970d558dc2d2af20945e9171a\System.Net.Requests.ni.dll
    ModLoad: 74c20000 74c74000   C:\WINDOWS\SYSTEM32\rasapi32.dll
    ModLoad: 74c00000 74c16000   C:\WINDOWS\SYSTEM32\rasman.dll
    ModLoad: 77670000 776c0000   C:\WINDOWS\SYSTEM32\WS2_32.dll
    ModLoad: 76e00000 76e08000   C:\WINDOWS\SYSTEM32\NSI.dll
    ModLoad: 74a50000 74a9a000   C:\WINDOWS\system32\mswsock.dll
    ModLoad: 73050000 730d3000   C:\WINDOWS\SYSTEM32\winhttp.dll
    ModLoad: 74bd0000 74bf2000   C:\WINDOWS\SYSTEM32\IPHLPAPI.DLL
    ModLoad: 747e0000 747e8000   C:\WINDOWS\SYSTEM32\WINNSI.DLL
    ModLoad: 747d0000 747e0000   C:\WINDOWS\SYSTEM32\dhcpcsvc6.DLL
    ModLoad: 747b0000 747c2000   C:\WINDOWS\SYSTEM32\dhcpcsvc.DLL
    ModLoad: 72590000 72605000   C:\WINDOWS\SYSTEM32\DNSAPI.dll
    ModLoad: 5ce90000 5cfd6000   C:\WINDOWS\system32\windowscodecs.dll
    ModLoad: 73740000 73747000   C:\Windows\System32\rasadhlp.dll
    ModLoad: 74770000 747af000   C:\WINDOWS\System32\fwpuclnt.dll
    ModLoad: 73b20000 73b29000   C:\WINDOWS\SYSTEM32\secur32.dll
    ModLoad: 5f8a0000 5f8f4000   C:\WINDOWS\SYSTEM32\schannel.dll
    ModLoad: 76fa0000 77128000   C:\WINDOWS\SYSTEM32\CRYPT32.dll
    ModLoad: 753b0000 753c2000   C:\WINDOWS\SYSTEM32\MSASN1.dll
    ModLoad: 721c0000 721d9000   C:\WINDOWS\SYSTEM32\ncrypt.dll
    ModLoad: 72170000 72197000   C:\WINDOWS\SYSTEM32\NTASN1.dll
    ModLoad: 5f670000 5f685000   C:\WINDOWS\system32\ncryptsslp.dll
    ModLoad: 72150000 7216d000   C:\WINDOWS\SYSTEM32\gpapi.dll
    ModLoad: 63dc0000 63e87000   C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\System.Servd1dec626#\df55f04bc0ebe6c1abde4bc467bf4d03\System.ServiceModel.Internals.ni.dll
    ModLoad: 3a110000 3a12b000   C:\WINDOWS\SYSTEM32\userenv.dll
    ModLoad: 37020000 3702e000   C:\WINDOWS\SYSTEM32\profext.dll
    ModLoad: 3ad90000 3adc0000   C:\WINDOWS\System32\wpnapps.dll
    (3b08.298c): Unknown exception - code c000027b (!!! second chance !!!)
    *** ERROR: Symbol file could not be found.  Defaulted to export symbols for C:\WINDOWS\SYSTEM32\ntdll.dll -
    *** ERROR: Symbol file could not be found.  Defaulted to export symbols for C:\WINDOWS\SYSTEM32\combase.dll -
    *** ERROR: Symbol file could not be found.  Defaulted to export symbols for C:\Windows\System32\Windows.UI.Xaml.dll -
    eax=0f20f0f0 ebx=0f20f0f0 ecx=00000000 edx=00000000 esi=0f20f418 edi=6a42bfe8
    eip=777a272e esp=0f20f3d4 ebp=0f20f474 iopl=0         nv up ei pl nz ac po nc
    cs=0023  ss=002b  ds=002b  es=002b  fs=0053  gs=002b             efl=00000212
    combase!RoFailFastWithErrorContextInternal+0x112:
    777a272e 6a03            push    3
    0:006> x windows_ui_xaml!g_dwErrorContextTlsIndex
    0:006> kp
    ChildEBP RetAddr 
    WARNING: Stack unwind information not available. Following frames may be wrong.
    0f20f474 00000000 combase!RoFailFastWithErrorContextInternal+0x112
    0:006>  !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Exception Analysis                                   *
    *                                                                             *
    *******************************************************************************

    ***** OS symbols are WRONG. Please fix symbols to do analysis.

    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Either you specified an unqualified symbol, or your debugger   ***
    ***    doesn't have full symbol information.  Unqualified symbol      ***
    ***    resolution is turned off by default. Please either specify a   ***
    ***    fully qualified symbol module!symbolname, or enable resolution ***
    ***    of unqualified symbols by typing ".symopt- 100". Note that   ***
    ***    enabling unqualified symbol resolution with network symbol     ***
    ***    server shares in the symbol path may cause the debugger to     ***
    ***    appear to hang for long periods of time when an incorrect      ***
    ***    symbol name is typed or the network symbol server is down.     ***
    ***                                                                   ***
    ***    For some commands to work properly, your symbol path           ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: ntdll!_PEB                                    ***
    ***                                                                   ***
    *************************************************************************
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    *                                                                   *
    * The Symbol Path can be set by:                                    *
    *   using the _NT_SYMBOL_PATH environment variable.                 *
    *   using the -y <symbol_path> argument when starting the debugger. *
    *   using .sympath and .sympath+                                    *
    *********************************************************************
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    *                                                                   *
    * The Symbol Path can be set by:                                    *
    *   using the _NT_SYMBOL_PATH environment variable.                 *
    *   using the -y <symbol_path> argument when starting the debugger. *
    *   using .sympath and .sympath+                                    *
    *********************************************************************
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    *                                                                   *
    * The Symbol Path can be set by:                                    *
    *   using the _NT_SYMBOL_PATH environment variable.                 *
    *   using the -y <symbol_path> argument when starting the debugger. *
    *   using .sympath and .sympath+                                    *
    *********************************************************************
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    *                                                                   *
    * The Symbol Path can be set by:                                    *
    *   using the _NT_SYMBOL_PATH environment variable.                 *
    *   using the -y <symbol_path> argument when starting the debugger. *
    *   using .sympath and .sympath+                                    *
    *********************************************************************
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    *                                                                   *
    * The Symbol Path can be set by:                                    *
    *   using the _NT_SYMBOL_PATH environment variable.                 *
    *   using the -y <symbol_path> argument when starting the debugger. *
    *   using .sympath and .sympath+                                    *
    *********************************************************************
    GetContextState failed, 0x80070057
    GetContextState failed, 0x80070057
    GetContextState failed, 0x80070057

    Monday, September 24, 2012 9:02 PM
  • The event viewer shows this:

    Faulting application name: EventBoard.W8.exe, version: 5.3.0.0, time stamp: 0x5060cb38

    Faulting module name: Windows.UI.Xaml.dll, version: 6.2.9200.16384, time stamp: 0x501096e5

    Exception code: 0xc000027b

    Fault offset: 0x007bde82

    Faulting process id: 0x2850

    Faulting application start time: 0x01cd9a9a3cc8b1fb

    Faulting application path: D:\Source\SVCCViewer\WP7CCViewer\EventBoard.W8\bin\Debug\AppX\EventBoard.W8.exe

    Faulting module path: C:\Windows\System32\Windows.UI.Xaml.dll

    Report Id: 8107aca4-068d-11e2-be70-0090f59567ce

    Faulting package full name: FalafelSoftwareInc.EventBoard_5.3.0.39_neutral__5hk9g6r40fw2m

    Faulting package-relative application ID: App

    Monday, September 24, 2012 9:21 PM
  • Here is a captured dump: http://sdrv.ms/Omr8a9
    Monday, September 24, 2012 10:47 PM
  • Interesting part?

    So, I bind my GridView (and a ListView, for Snapped view) to this list of ViewModels that I populate with the results of my JSON REST service call.

    I see the grid view render with all it's data and then it immediately dies. The objects are not disposed of or anything such, and this is the same code that has worked for ages.

    It makes me wonder if something changed in the GridView drawing code?

    (2658.4f1c): Unknown exception - code c000027b (!!! second chance !!!)
    eax=0e79f5d8 ebx=0e79f5d8 ecx=00000000 edx=00000000 esi=0e79f900 edi=4fbdafe8
    eip=777a272e esp=0e79f8bc ebp=0e79f95c iopl=0         nv up ei pl nz ac pe nc
    cs=0023  ss=002b  ds=002b  es=002b  fs=0053  gs=002b             efl=00000216
    combase!RoFailFastWithErrorContextInternal+0x112:
    777a272e 6a03            push    3
    0:006> kp
    ChildEBP RetAddr 
    0e79f95c 0dabde82 combase!RoFailFastWithErrorContextInternal(HRESULT hrError = 0x8000ffff, unsigned long cStowedExceptions = 1, struct _STOWED_EXCEPTION_INFORMATION_V1 ** aStowedExceptionPointers = 0x4fbdafe8)+0x112 [d:\w8rtm\com\combase\winrt\error\error.cpp @ 853]
    0e79fa18 0d37e720 Windows_UI_Xaml!CCoreServices::NWDrawTree+0x740b11 [d:\w8rtm\windows\dxaml\xcp\core\dll\xcpcore.cpp @ 10985]
    0e79fa58 0d37df2b Windows_UI_Xaml!CCoreServices::NWDrawMainTree(struct ICoreRenderTarget * pIRenderTarget = 0x1269afbc, unsigned int fForceRedraw = 0, unsigned int needsToReleaseHardwareResources = 0, struct XRECT_WH * prcDirtyRect = 0x0e79fa9c)+0x2aa [d:\w8rtm\windows\dxaml\xcp\core\dll\xcpcore.cpp @ 10693]
    (Inline) -------- Windows_UI_Xaml!CRenderTarget::DrawInternal+0x2a [d:\w8rtm\windows\dxaml\xcp\core\compositor\rendertarget.cpp @ 220]
    0e79fa7c 0d37e455 Windows_UI_Xaml!CWindowRenderTarget::Draw(struct ICoreServices * pCore = 0x0ede0a30, unsigned int fForceRedraw = 0, struct XRECT_WH * prcDirtyRect = 0x0e79fa9c)+0x75 [d:\w8rtm\windows\dxaml\xcp\core\compositor\windowrendertarget.cpp @ 128]
    0e79fab0 0d37e102 Windows_UI_Xaml!CXcpBrowserHost::OnTick(void)+0x19c [d:\w8rtm\windows\dxaml\xcp\host\win\browserdesktop\winbrowserhost.cpp @ 1160]
    0e79facc 0d37e261 Windows_UI_Xaml!CXcpDispatcher::Tick(void)+0xc3 [d:\w8rtm\windows\dxaml\xcp\win\shared\xcpwindow.cpp @ 1120]
    0e79fae0 0d324473 Windows_UI_Xaml!CXcpDispatcher::OnReentrancyProtectedWindowMessage(unsigned int msg = 0x402, unsigned int wParam = 0, long lParam = 0n0)+0x32 [d:\w8rtm\windows\dxaml\xcp\win\shared\xcpwindow.cpp @ 653]
    (Inline) -------- Windows_UI_Xaml!CXcpDispatcher::ProcessMessage+0x28 [d:\w8rtm\windows\dxaml\xcp\win\shared\xcpwindow.cpp @ 457]
    0e79fb00 753d77d8 Windows_UI_Xaml!CXcpDispatcher::WindowProc(struct HWND__ * hwnd = 0x00540464, unsigned int msg = 0x402, unsigned int wParam = 0, long lParam = 0n0)+0x6a [d:\w8rtm\windows\dxaml\xcp\win\shared\xcpwindow.cpp @ 401]
    0e79fb2c 753d78cb USER32!InternalCallWinProc+0x23
    0e79fba8 753d899d USER32!UserCallWinProcCheckWow+0x100
    0e79fc1c 753d8a66 USER32!DispatchMessageWorker+0x3ef
    0e79fc2c 53bf11dc USER32!DispatchMessageW+0x10
    0e79fc68 53bf1290 windows_ui!Windows::UI::Core::CDispatcher::ProcessMessage(int bDrainQueue = 0n1, int * pbAnyMessages = 0x0e79fc88)+0xc9 [d:\w8rtm\windows\advcore\winrt\iwindow\corewindow\dispatcher.cpp @ 121]
    0e79fcdc 0d48dee2 windows_ui!Windows::UI::Core::CDispatcher::ProcessEvents(Windows::UI::Core::CoreProcessEventsOption options = CoreProcessEventsOption_ProcessUntilQuit (0n2))+0x7a [d:\w8rtm\windows\advcore\winrt\iwindow\corewindow\dispatcher.cpp @ 184]
    0e79fcf4 0d48dea1 Windows_UI_Xaml!CJupiterWindow::RunCoreWindowMessageLoop(void)+0x33 [d:\w8rtm\windows\dxaml\xcp\dxaml\hosting\jupiterwindow.cpp @ 416]
    0e79fd1c 0d48de65 Windows_UI_Xaml!CJupiterControl::RunMessageLoop(void)+0x28 [d:\w8rtm\windows\dxaml\xcp\dxaml\hosting\jupitercontrol.cpp @ 714]
    0e79fd34 0d48de40 Windows_UI_Xaml!DirectUI::DXamlCore::RunMessageLoop(void)+0x29 [d:\w8rtm\windows\dxaml\xcp\dxaml\lib\dxamlcore.cpp @ 2539]
    0e79fd38 0fb4c9dd Windows_UI_Xaml!DirectUI::FrameworkView::Run(void)+0xc [d:\w8rtm\windows\dxaml\xcp\dxaml\lib\frameworkview_partial.cpp @ 91]
    0e79fd44 0fb4cab2 twinapi!Windows::ApplicationModel::Core::CoreApplicationView::Run(void)+0x27 [d:\w8rtm\shell\coreapplication\application\lib\coreapplicationview.cpp @ 889]
    0e79fd64 0fb4c9f6 twinapi!`Windows::ApplicationModel::Core::CoreApplicationViewAgileContainer::RuntimeClassInitialize'::`55'::<lambda_A2234BA2CCD64E2C>::operator()(void * pv = 0x0cf62f80)+0xb2 [d:\w8rtm\shell\coreapplication\application\lib\coreapplicationview.cpp @ 560]
    0e79fd70 749f1ffd twinapi!`Windows::ApplicationModel::Core::CoreApplicationViewAgileContainer::RuntimeClassInitialize'::`55'::<lambda_A2234BA2CCD64E2C>::<helper_func>(void * pv = 0x0cf62f80)+0xe [d:\w8rtm\shell\coreapplication\application\lib\coreapplicationview.cpp @ 613]
    0e79fde8 607e64d0 shcore!SHWaitForThreadWithWakeMask+0x13b
    0e79fe20 76828543 vfbasics!AVrfpStandardThreadFunction+0x3c
    0e79fe2c 7792ac69 KERNEL32!BaseThreadInitThunk+0xe
    0e79fe70 7792ac3c ntdll!__RtlUserThreadStart+0x72
    0e79fe88 00000000 ntdll!_RtlUserThreadStart+0x1b

    Monday, September 24, 2012 11:51 PM
  • One more interesting detail. The GridView contains a binding to a LogoURI property, which is a property of the viewmodel. If I remove that from the Data Template, no crash. The URIs point to images on our CDN and are valid. The property returns String.Empty of the URI is null or empty. The grid is bound to a CollectionViewSource, which is bound to an ObservableCollection of ConferenceInfoViewModels, populated by the JSON query....

    <DataTemplate>
        <Grid HorizontalAlignment="Left" Width="250" Height="250">
            <Grid.RowDefinitions>
                <RowDefinition Height="70"/>
                <RowDefinition Height="155"/>
            </Grid.RowDefinitions>
            <Image Source="{Binding LogoUri}" HorizontalAlignment="Left" VerticalAlignment="Top" />
            <Grid Grid.Row="1" Margin="0,15,0,0">
                <Grid.RowDefinitions>
                    <RowDefinition Height="Auto" />
                    <RowDefinition Height="Auto" />
                    <RowDefinition Height="*" />
                </Grid.RowDefinitions>
                <TextBlock Grid.Row="0" Text="{Binding Path=Name}" HorizontalAlignment="Left" FontSize="20" FontWeight="Bold" TextWrapping="Wrap" Style="{StaticResource TitleTextStyle}" />
                <TextBlock Grid.Row="1" Margin="0,5,0,0" HorizontalAlignment="Left" Style="{StaticResource CaptionTextStyle}" FontWeight="Bold" Foreground="White" TextWrapping="Wrap">
            <Run Text="{Binding Path=Location}"/>
            <Run Text=", "/>
            <Run Text="{Binding Path=Duration}" />
                </TextBlock>
                <TextBlock Grid.Row="2" Margin="0,10,0,0" Text="{Binding Path=Description}" HorizontalAlignment="Left" TextTrimming="WordEllipsis" TextWrapping="Wrap" Style="{StaticResource BodyTextStyle}" />
            </Grid>
        </Grid>
    </DataTemplate>

    Tuesday, September 25, 2012 12:33 AM
  • Unfortunately your dump doesn't have the issue I was hoping it had, rather the one you provided is crashing when trying to create a D3D11 Texture object and failing due to being out of memory.   It's possible this is related to graphics drivers on the machine changing, other processes creating a greater memory load to the device, or variance in the results from your query (since it seems that the number of elements returned from the JSON query is proportional to the number of things attempted to be rendered.)

    I've forwarded this thread on to some folks from the graphics team to see if they can make other suggestions.

    -Matt


    XAML SDET Lead : Input / DirectManipulation / Accessibility

    Tuesday, September 25, 2012 4:23 PM
  • The odd thing is it has worked for over a year on the same machine. What triggered this was I saw the WACK test failed suddenly when I went to submit an update. I then found that the version in the store (Eventboard) also dies on the machine it always worked on. It seemed that something external to the app had changed. The amount of data is similar to earlier, some 100 images are rendered.

    Tuesday, September 25, 2012 6:18 PM
  • Also, if I monitor memory usage as I launch the app, there is still 3.5GB left of 12 at the point where it crashes.

    Here is another run after rebooting

    21f4.1fb8): Unknown exception - code c000027b (!!! second chance !!!)
    eax=0f64f198 ebx=0f64f198 ecx=00000000 edx=00000000 esi=0f64f4c0 edi=51d60fe8
    eip=7695272e esp=0f64f47c ebp=0f64f51c iopl=0         nv up ei pl nz ac po nc
    cs=0023  ss=002b  ds=002b  es=002b  fs=0053  gs=002b             efl=00000212
    combase!RoFailFastWithErrorContextInternal+0x112:
    7695272e 6a03            push    3
    0:006> kp
    ChildEBP RetAddr 
    0f64f51c 00000000 combase!RoFailFastWithErrorContextInternal(HRESULT hrError = <Memory access error>, unsigned long cStowedExceptions = <Memory access error>, struct _STOWED_EXCEPTION_INFORMATION_V1 ** aStowedExceptionPointers = <Memory access error>)+0x112 [d:\w8rtm\com\combase\winrt\error\error.cpp @ 853]

    Tuesday, September 25, 2012 6:25 PM
  • When I limit the result set to 60 items, I get them to show, and a different silent exception when I shut down the app. What is with all these silent exceptions? It is impossible to debug when I don't get anything actual to work on!

    eax=000001a1 ebx=00000000 ecx=0ed28fc0 edx=00000000 esi=6c7bdb58 edi=000001ff
    eip=6c7b3355 esp=0ef4e488 ebp=0ef4e68c iopl=0         nv up ei pl nz na po nc
    cs=0023  ss=002b  ds=002b  es=002b  fs=0053  gs=002b             efl=00000202
    vrfcore!VerifierStopMessageEx+0x578:
    6c7b3355 cc              int     3
    0:006> kp
    ChildEBP RetAddr 
    0ef4e68c 00000000 vrfcore!VerifierStopMessageEx+0x578

    I cant get a dump of this

    Creating d:\dumps\eb3.dmp - mini user dump
    GetContextState failed, 0x80070057
    Unable to get event thread context, Win32 error 0n87
    GenGetProcessInfo.Start(0x2cd8) failed, 0x8007012b
    Dump creation failed, Win32 error 0n299
        "Only part of a ReadProcessMemory or WriteProcessMemory request was completed."

    Tuesday, September 25, 2012 6:41 PM
  • Seeing vrfcore!VerifierStopMessageEx indicates you have AppVerifier turned on.  The error on shutdown is likely something you can read in the AppVerifier logs under  %ALLUSERSPROFILE%\AppVerifierLog.

    Since AppVerifier can also be used to simulate low-memory conditions, you might want to check whether this got left on using the AppVerif UI.  (Make sure "Low Resource Simulation" is not set for your app.

    Hope this helps,
    Matt


    XAML SDET Lead : Input / DirectManipulation / Accessibility

    • Marked as answer by FalafelSoftware Wednesday, September 26, 2012 12:20 AM
    Tuesday, September 25, 2012 7:28 PM
  • Interesting lead. I have a C:\Users\jwaters\AppVerifierLogs folder but it is empty. How do I run the UI or configure it? Evidently it is doing something....
    Tuesday, September 25, 2012 10:40 PM
  • Could it have been turned on by the WACK test?
    Tuesday, September 25, 2012 10:49 PM
  • OK, so I found it under c:\windows\system32\appverif.exe. I turned off all the tests, and voila, my app works again...

    I have no idea how it got turned on, could it have been the WACK tool?

    Now back to debugging the original issue, which was the WACK tool reporting that the app crashed...maybe that was in low memory conditions? In that case, what can I do, since no exception is thrown...how can I prevent that happening?

    Tuesday, September 25, 2012 11:10 PM
  • Glad we got to the bottom of it.  While AppVerifier is part of the SDK, I don't believe (90% certainty here) that WACK testing turns on AppVerifier, especially for fault simulation purposes.  We use AppVerifier locally to look for bugs and validate the framework fails as expected in these circumstances, and the only thing you'd expect when running out of memory is a hard, fast exception. 

    In short, I don't think you can prevent OOM exceptions thrown from within Framework APIs, nor really do anything useful in response to them.   If WACK tool still says your app is crashing for other reasons, get the dump or stack and we can explore from there.  In the mean time, I'll ping a couple folks and see if I can get the official word on WACK + AppV.

    -Matt


    XAML SDET Lead : Input / DirectManipulation / Accessibility

    Wednesday, September 26, 2012 9:15 PM
  • Thanks Matt.

    I did capture a WACK crash and logged it with a dump in another post; http://social.msdn.microsoft.com/Forums/en-US/winappswithcsharp/thread/2ef28399-5807-4885-b1fa-1cf5f9c77cb8

    Wednesday, September 26, 2012 9:16 PM
  • At least on my machine, %ALLUSERSPROFILE%=C:\ProgramData, not the Users folder for your account.

    XAML SDET Lead : Input / DirectManipulation / Accessibility

    Wednesday, September 26, 2012 9:21 PM
  • I checked with the appropriate folks, and turning on AppVerifier is not part of default WACK process.  Perhaps a coworker was being funny :).

    The stack in the other thread is unfamiliar but I'll take a peek @ the dump.

    -Matt


    XAML SDET Lead : Input / DirectManipulation / Accessibility

    Thursday, September 27, 2012 12:12 AM
  • Thanks for looking into that. Maybe I should scale back on the vodka ;-)
    Thursday, September 27, 2012 12:14 AM