locked
Accidental crash of application

    Question

  • I am developing a Window Store app and have a problem now. When I run the app with debugger, it works normally.

    When I run it without debugger, it crashed frequently - without obvious reason.

    The WER says, MoAppHang. Here is the latest WER report (the texts are in Russian language because I run the program on Russian version of Windows).

    Version=1
    EventType=MoAppHang
    EventTime=130129054484214905
    ReportType=3
    Consent=1
    ReportIdentifier=c111e724-bba2-11e2-be90-88532e95377d
    IntegratorReportIdentifier=c111e725-bba2-11e2-be90-88532e95377d
    WOW64=1
    NsAppName=praid:App
    Response.type=4
    Sig[0].Name=Полное имя пакета
    Sig[0].Value=SpecialistMetroApp_1.0.0.0_x86__96zs3djwa88zp
    Sig[1].Name=Имя приложения
    Sig[1].Value=praid:App
    Sig[2].Name=Версия приложения
    Sig[2].Value=0.0.0.0
    Sig[3].Name=Отметка времени приложения
    Sig[3].Value=51909a75
    Sig[4].Name=Сигнатура зависания
    Sig[4].Value=4974
    Sig[5].Name=Тип зависания
    Sig[5].Value=2097408
    DynamicSig[1].Name=Версия ОС
    DynamicSig[1].Value=6.2.9200.2.0.0.256.48
    DynamicSig[2].Name=Код языка
    DynamicSig[2].Value=1049
    DynamicSig[22].Name=Доп. сигнатура зависания 1
    DynamicSig[22].Value=49740af740ac531da29b6574954846d9
    DynamicSig[23].Name=Доп. сигнатура зависания 2
    DynamicSig[23].Value=b926
    DynamicSig[24].Name=Доп. сигнатура зависания 3
    DynamicSig[24].Value=b92696334d9cdaf112f3b3559068f19d
    DynamicSig[25].Name=Доп. сигнатура зависания 4
    DynamicSig[25].Value=4974
    DynamicSig[26].Name=Доп. сигнатура зависания 5
    DynamicSig[26].Value=49740af740ac531da29b6574954846d9
    DynamicSig[27].Name=Доп. сигнатура зависания 6
    DynamicSig[27].Value=b926
    DynamicSig[28].Name=Доп. сигнатура зависания 7
    DynamicSig[28].Value=b92696334d9cdaf112f3b3559068f19d
    UI[3]=SpecialistMetro.exe не отвечает
    UI[4]=Windows может поискать решение проблемы в Интернете. При закрытии не отвечающей программы может быть потеряна несохраненная информация.
    UI[5]=Выполнить поиск решения и закрыть программу
    UI[6]=Выполнить поиск решения и закрыть программу
    LoadedModule[0]=C:\Users\jacob\AppxLayouts\SpecialistMetroAppVS.Debug_Win32.jacob\SpecialistMetro.exe
    LoadedModule[1]=C:\Windows\SYSTEM32\ntdll.dll
    LoadedModule[2]=C:\Windows\SYSTEM32\KERNEL32.DLL
    LoadedModule[3]=C:\Windows\SYSTEM32\KERNELBASE.dll
    LoadedModule[4]=C:\Users\jacob\AppxLayouts\SpecialistMetroAppVS.Debug_Win32.jacob\libwebp.dll
    LoadedModule[5]=C:\Windows\SYSTEM32\d3d11.dll
    LoadedModule[6]=C:\Windows\SYSTEM32\d2d1.dll
    LoadedModule[7]=C:\Windows\SYSTEM32\shcore.dll
    LoadedModule[8]=C:\Program Files\WindowsApps\Microsoft.VCLibs.110.00.Debug_11.0.51106.1_x86__8wekyb3d8bbwe\vccorlib110d.DLL
    LoadedModule[9]=C:\Program Files\WindowsApps\Microsoft.VCLibs.110.00.Debug_11.0.51106.1_x86__8wekyb3d8bbwe\MSVCP110D.dll
    LoadedModule[10]=C:\Windows\SYSTEM32\ole32.dll
    LoadedModule[11]=C:\Program Files\WindowsApps\Microsoft.VCLibs.110.00.Debug_11.0.51106.1_x86__8wekyb3d8bbwe\MSVCR110D.dll
    LoadedModule[12]=C:\Windows\SYSTEM32\ADVAPI32.dll
    LoadedModule[13]=C:\Windows\SYSTEM32\combase.dll
    LoadedModule[14]=C:\Windows\SYSTEM32\msvcrt.dll
    LoadedModule[15]=C:\Windows\SYSTEM32\dxgi.dll
    LoadedModule[16]=C:\Windows\SYSTEM32\user32.dll
    LoadedModule[17]=C:\Windows\SYSTEM32\gdi32.dll
    LoadedModule[18]=C:\Windows\SYSTEM32\OLEAUT32.dll
    LoadedModule[19]=C:\Windows\SYSTEM32\RPCRT4.dll
    LoadedModule[20]=C:\Windows\SYSTEM32\sechost.dll
    LoadedModule[21]=C:\Windows\SYSTEM32\SspiCli.dll
    LoadedModule[22]=C:\Windows\SYSTEM32\CRYPTBASE.dll
    LoadedModule[23]=C:\Windows\SYSTEM32\bcryptPrimitives.dll
    LoadedModule[24]=C:\Windows\system32\IMM32.DLL
    LoadedModule[25]=C:\Windows\SYSTEM32\MSCTF.dll
    LoadedModule[26]=C:\Windows\System32\Windows.UI.Xaml.dll
    LoadedModule[27]=C:\Windows\SYSTEM32\NInput.dll
    LoadedModule[28]=C:\Windows\SYSTEM32\SHELL32.dll
    LoadedModule[29]=C:\Windows\SYSTEM32\SHLWAPI.dll
    LoadedModule[30]=C:\Windows\SYSTEM32\WININET.dll
    LoadedModule[31]=C:\Windows\SYSTEM32\dwmapi.dll
    LoadedModule[32]=C:\Windows\SYSTEM32\UxTheme.dll
    LoadedModule[33]=C:\Windows\SYSTEM32\wintypes.dll
    LoadedModule[34]=C:\Windows\SYSTEM32\urlmon.dll
    LoadedModule[35]=C:\Windows\SYSTEM32\UIAutomationCore.DLL
    LoadedModule[36]=C:\Windows\SYSTEM32\TWINAPI.dll
    LoadedModule[37]=C:\Windows\SYSTEM32\iertutil.dll
    LoadedModule[38]=C:\Windows\SYSTEM32\CRYPTSP.dll
    LoadedModule[39]=C:\Windows\system32\rsaenh.dll
    LoadedModule[40]=C:\Program Files (x86)\Common Files\microsoft shared\ink\tiptsf.dll
    LoadedModule[41]=C:\Windows\SYSTEM32\actxprxy.dll
    LoadedModule[42]=C:\Windows\SYSTEM32\Windows.UI.Immersive.dll
    LoadedModule[43]=C:\Windows\SYSTEM32\DUI70.dll
    LoadedModule[44]=C:\Windows\SYSTEM32\dwrite.dll
    LoadedModule[45]=C:\Windows\SYSTEM32\DXGIDebug.dll
    LoadedModule[46]=C:\Windows\SYSTEM32\D3D10Warp.dll
    LoadedModule[47]=C:\Windows\SYSTEM32\MrmCoreR.dll
    LoadedModule[48]=C:\Windows\SYSTEM32\Bcp47Langs.dll
    LoadedModule[49]=C:\Windows\SYSTEM32\profapi.dll
    LoadedModule[50]=C:\Windows\SYSTEM32\igd10umd32.dll
    LoadedModule[51]=C:\Windows\system32\CLRHost.dll
    LoadedModule[52]=C:\Windows\SYSTEM32\mscoree.dll
    LoadedModule[53]=C:\Windows\Microsoft.NET\Framework\v4.0.30319\mscoreei.dll
    LoadedModule[54]=C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll
    LoadedModule[55]=C:\Windows\SYSTEM32\MSVCR110_CLR0400.dll
    LoadedModule[56]=C:\Windows\System32\Windows.ApplicationModel.dll
    LoadedModule[57]=C:\Windows\assembly\NativeImages_v4.0.30319_32\mscorlib\374a0cc6603f58864831897ef723bd4a\mscorlib.ni.dll
    LoadedModule[58]=C:\Windows\assembly\NativeImages_v4.0.30319_32\System.Runtime\eefb742daaf569aaf55c103d9c693760\System.Runtime.ni.dll
    LoadedModule[59]=C:\Windows\assembly\NativeImages_v4.0.30319_32\Windows.UI.Xaml\247d2cd8d760bda4cb54209a9b8a7a5a\Windows.UI.Xaml.ni.dll
    LoadedModule[60]=C:\Windows\Microsoft.NET\Framework\v4.0.30319\clrjit.dll
    LoadedModule[61]=C:\Windows\assembly\NativeImages_v4.0.30319_32\System.Collections\ab6baaddc2322e1768e9e784e1cb8e9e\System.Collections.ni.dll
    LoadedModule[62]=C:\Windows\SYSTEM32\bcrypt.dll
    LoadedModule[63]=C:\Windows\assembly\NativeImages_v4.0.30319_32\System.Runtbff93e24#\56a2b3e257edcb5ddef95f5b2e2ea705\System.Runtime.InteropServices.WindowsRuntime.ni.dll
    LoadedModule[64]=C:\Windows\assembly\NativeImages_v4.0.30319_32\Windows.Foundation\030af73956dbebe8823385e9c822172b\Windows.Foundation.ni.dll
    LoadedModule[65]=C:\Windows\SYSTEM32\windows.ui.dll
    LoadedModule[66]=C:\Windows\SYSTEM32\dcomp.dll
    LoadedModule[67]=C:\Users\jacob\AppxLayouts\SpecialistMetroAppVS.Debug_Win32.jacob\SSLSocket.dll
    LoadedModule[68]=C:\Users\jacob\AppxLayouts\SpecialistMetroAppVS.Debug_Win32.jacob\LIBEAY32.dll
    LoadedModule[69]=C:\Users\jacob\AppxLayouts\SpecialistMetroAppVS.Debug_Win32.jacob\SSLEAY32.dll
    LoadedModule[70]=C:\Windows\SYSTEM32\WS2_32.dll
    LoadedModule[71]=C:\Users\jacob\AppxLayouts\SpecialistMetroAppVS.Debug_Win32.jacob\MSVCR100D.dll
    LoadedModule[72]=C:\Windows\SYSTEM32\NSI.dll
    LoadedModule[73]=C:\Windows\System32\CryptoWinRT.dll
    LoadedModule[74]=C:\Windows\SYSTEM32\ncrypt.dll
    LoadedModule[75]=C:\Windows\SYSTEM32\CRYPT32.dll
    LoadedModule[76]=C:\Windows\SYSTEM32\NTASN1.dll
    LoadedModule[77]=C:\Windows\SYSTEM32\MSASN1.dll
    LoadedModule[78]=C:\Windows\System32\Windows.Storage.ApplicationData.dll
    LoadedModule[79]=C:\Windows\SYSTEM32\PROPSYS.dll
    LoadedModule[80]=C:\Windows\SYSTEM32\msftedit.dll
    LoadedModule[81]=C:\Windows\SYSTEM32\DPAPI.DLL
    LoadedModule[82]=C:\Windows\System32\Windows.Networking.Connectivity.dll
    LoadedModule[83]=C:\Windows\SYSTEM32\DNSAPI.dll
    LoadedModule[84]=C:\Windows\SYSTEM32\IPHLPAPI.DLL
    LoadedModule[85]=C:\Windows\SYSTEM32\WINNSI.DLL
    LoadedModule[86]=C:\Windows\SYSTEM32\dhcpcsvc6.DLL
    LoadedModule[87]=C:\Windows\SYSTEM32\dhcpcsvc.DLL
    LoadedModule[88]=C:\Windows\system32\mswsock.dll
    LoadedModule[89]=C:\Windows\System32\rasadhlp.dll
    LoadedModule[90]=C:\Windows\System32\msxml6.dll
    LoadedModule[91]=C:\Windows\SYSTEM32\Secur32.dll
    LoadedModule[92]=C:\Windows\SYSTEM32\winhttp.dll
    LoadedModule[93]=C:\Windows\SYSTEM32\userenv.dll
    LoadedModule[94]=C:\Windows\SYSTEM32\profext.dll
    LoadedModule[95]=C:\Windows\System32\fwpuclnt.dll
    LoadedModule[96]=C:\Windows\System32\wpnapps.dll
    LoadedModule[97]=C:\Windows\system32\windowscodecs.dll
    LoadedModule[98]=C:\Windows\SYSTEM32\oleacc.dll
    LoadedModule[99]=C:\Windows\SYSTEM32\schannel.dll
    LoadedModule[100]=C:\Windows\system32\ncryptsslp.dll
    LoadedModule[101]=C:\Windows\SYSTEM32\WINTRUST.dll
    LoadedModule[102]=C:\Windows\SYSTEM32\gpapi.dll
    LoadedModule[103]=C:\Windows\SYSTEM32\cryptnet.dll
    LoadedModule[104]=C:\Windows\SYSTEM32\WLDAP32.dll
    LoadedModule[105]=C:\Windows\System32\threadpoolwinrt.dll
    LoadedModule[106]=C:\Windows\SYSTEM32\DUser.dll
    LoadedModule[107]=C:\Windows\System32\Windows.Networking.dll
    LoadedModule[108]=C:\Windows\SYSTEM32\FirewallAPI.dll
    LoadedModule[109]=C:\Windows\SYSTEM32\MFPlat.DLL
    LoadedModule[110]=C:\Windows\SYSTEM32\cfgmgr32.dll
    LoadedModule[111]=C:\Windows\SYSTEM32\AVRT.dll
    LoadedModule[112]=C:\Windows\SYSTEM32\sxs.dll
    LoadedModule[113]=C:\Windows\System32\UIAnimation.dll
    File[0].CabName=SpecialistMetro.exe.xml
    File[0].Path=WER2827.tmp.xml
    File[0].Flags=327680
    File[0].Type=5
    File[0].Original.Path=C:\Users\jacob\AppData\Local\Temp\WER2827.tmp.xml
    File[1].CabName=WERInternalMetadata.xml
    File[1].Path=WER2828.tmp.WERInternalMetadata.xml
    File[1].Flags=327682
    File[1].Type=5
    File[1].Original.Path=C:\Users\jacob\AppData\Local\Temp\WER2828.tmp.WERInternalMetadata.xml
    File[2].CabName=memory.hdmp
    File[2].Path=WER2839.tmp.hdmp
    File[2].Flags=2097152
    File[2].Type=3
    File[2].Original.Path=C:\Users\jacob\AppData\Local\Temp\WER2839.tmp.hdmp
    File[3].CabName=triagedump.dmp
    File[3].Path=WER350B.tmp.dmp
    File[3].Flags=2424834
    File[3].Type=6
    File[3].Original.Path=C:\Users\jacob\AppData\Local\Temp\WER350B.tmp.dmp
    FriendlyEventName=Не отвечает и была закрыта
    ConsentKey=AppHangXProcB1
    AppName=SpecialistMetroApp_96zs3djwa88zp!App
    AppPath=C:\Users\jacob\AppxLayouts\SpecialistMetroAppVS.Debug_Win32.jacob\SpecialistMetro.exe
    ReportDescription=Ошибка привела к остановке взаимодействия программы с Windows.
    NsPartner=windows
    NsGroup=windows8

    Here is the output of the !analyze command in WinDbg:

    0:002> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Exception Analysis                                   *
    *                                                                             *
    *******************************************************************************

    *** WARNING: Unable to verify checksum for mscorlib.ni.dll
    *** WARNING: Unable to verify checksum for SpecialistMetro.exe
    Unable to load image C:\Users\jacob\AppxLayouts\SpecialistMetroAppVS.Debug_Win32.jacob\SSLSocket.dll, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for SSLSocket.dll
    Unable to load image C:\Users\jacob\AppxLayouts\SpecialistMetroAppVS.Debug_Win32.jacob\libeay32.dll, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for libeay32.dll
    *** ERROR: Module load completed but symbols could not be loaded for libeay32.dll
    *** WARNING: Unable to verify timestamp for ssleay32.dll
    *** ERROR: Module load completed but symbols could not be loaded for ssleay32.dll

    FAULTING_IP:
    +0
    00000000 ??              ???

    EXCEPTION_RECORD:  ffffffff -- (.exr 0xffffffffffffffff)
    ExceptionAddress: 00000000
       ExceptionCode: cfffffff (Application hang)
      ExceptionFlags: 00000001
    NumberParameters: 0

    BUGCHECK_STR:  HANG

    DEFAULT_BUCKET_ID:  APPLICATION_HANG

    PROCESS_NAME:  SpecialistMetro.exe

    ERROR_CODE: (NTSTATUS) 0xcfffffff - <Unable to get error code text>

    EXCEPTION_CODE: (NTSTATUS) 0xcfffffff - <Unable to get error code text>

    NTGLOBALFLAG:  2

    APPLICATION_VERIFIER_FLAGS:  0

    APP:  specialistmetro.exe

    MANAGED_STACK: !dumpstack -EE
    OS Thread Id: 0x19b0 (2)
    Current frame:
    ChildEBP RetAddr  Caller, Callee

    DERIVED_WAIT_CHAIN: 

    Dl Eid Cid     WaitType
    -- --- ------- --------------------------
       2   119c.19b0 Multi Handle          

    WAIT_CHAIN_COMMAND:  ~2s;k;;

    BLOCKING_THREAD:  000019b0

    PRIMARY_PROBLEM_CLASS:  APPLICATION_HANG

    LAST_CONTROL_TRANSFER:  from 76c0c752 to 76f81318

    FAULTING_THREAD:  00000002

    STACK_TEXT: 
    04b1f1b4 76c0c752 00000004 04b1f360 00000001 ntdll!NtWaitForMultipleObjects+0xc
    04b1f338 75e19879 00000004 00000000 00000000 KERNELBASE!WaitForMultipleObjectsEx+0x10b
    04b1f390 75e19778 00000003 00000000 ffffffff user32!RealMsgWaitForMultipleObjectsEx+0x16b
    04b1f3b0 76d9d4ab 00000003 04b1f458 ffffffff user32!MsgWaitForMultipleObjectsEx+0x3e
    04b1f3d4 76d9d397 04b1f578 04b1f458 ffffffff combase!ASTAWaitContext::KernelWait+0x2f
    04b1f540 76d9da07 04b1f578 00000001 052e10e0 combase!ASTAWaitContext::Wait+0x1e6
    04b1f5c4 76d9d96a 00000002 00000001 00000000 combase!ASTAWaitInNewContext+0x78
    04b1f5f4 76d88c23 00000000 ffffffff 00000000 combase!ASTAThreadWaitForHandles+0x4a
    04b1f61c 71eb5d08 00000018 ffffffff 00000001 combase!CoWaitForMultipleHandles+0xa4
    04b1f664 71eb5ea0 009ead50 00000184 04e7e240 twinapi!Windows::ApplicationModel::Core::CoreApplicationView::SuspendResume+0x1da
    04b1f684 6f02fdff 052f1a08 009ecb18 00000000 twinapi!Microsoft::WRL::Details::InvokeHelper<Microsoft::WRL::Implements<Microsoft::WRL::RuntimeClassFlags<2>,Windows::UI::Core::IDispatchedHandler,Microsoft::WRL::FtmBase,Microsoft::WRL::Details::Nil,Microsoft::WRL::Details::Nil,Microsoft::WRL::Details::Nil,Microsoft::WRL::Details::Nil,Microsoft::WRL::Details::Nil,Microsoft::WRL::Details::Nil,Microsoft::WRL::Details::Nil>,`Windows::ApplicationModel::Core::CoreApplicationViewAgileContainer::Suspend'::`6'::<lambda_3826D244AEABACB1>,0>::Invoke+0x40
    04b1f6cc 6f0214ae 009ecc80 00000000 00008064 windows_ui!Windows::UI::Core::CDispatcher::ProcessInvokeItem+0x13f
    04b1f6f0 75e177d8 003104ca 00008064 00000000 windows_ui!Windows::UI::Core::WindowServer::WndProc+0x1e3
    04b1f71c 75e178cb 6f0212d4 003104ca 00008064 user32!InternalCallWinProc+0x23
    04b1f798 75e1bd11 6f0212d4 6f0212d4 00000000 user32!UserCallWinProcCheckWow+0x100
    04b1f7d4 75e1bd39 003104ca 00000000 00000000 user32!CallWindowProcAorW+0xb1
    04b1f7f0 7214b348 6f0212d4 003104ca 00008064 user32!CallWindowProcW+0x1c
    04b1f814 7214b2c3 003104ca 00000000 00000000 Windows_UI_Xaml!CJupiterWindow::WindowProc+0x76
    04b1f830 75e177d8 003104ca 00008064 00000000 Windows_UI_Xaml!CJupiterWindow::StaticWindowProc+0x29
    04b1f85c 75e178cb 7214b296 003104ca 00008064 user32!InternalCallWinProc+0x23
    04b1f8d8 75e1899d 7214b296 7214b296 00000000 user32!UserCallWinProcCheckWow+0x100
    04b1f94c 75e18a66 00000000 00008064 04b1f998 user32!DispatchMessageWorker+0x3ef
    04b1f95c 6f0211dc 04b1f97c 00000000 00000002 user32!DispatchMessageW+0x10
    04b1f998 6f021290 00000001 04b1f9b8 04639100 windows_ui!Windows::UI::Core::CDispatcher::ProcessMessage+0xc9
    04b1fa0c 7224df12 009ecc80 00000002 00000000 windows_ui!Windows::UI::Core::CDispatcher::ProcessEvents+0x7a
    04b1fa24 7224ded1 009ea118 009ea18c 009ea118 Windows_UI_Xaml!CJupiterWindow::RunCoreWindowMessageLoop+0x33
    04b1fa4c 7224de95 009ea18c 009ea118 76f901a0 Windows_UI_Xaml!CJupiterControl::RunMessageLoop+0x28
    04b1fa64 7224de70 71e9c9dd 00d6ce64 04b1fa94 Windows_UI_Xaml!DirectUI::DXamlCore::RunMessageLoop+0x29
    04b1fa68 71e9c9dd 00d6ce64 04b1fa94 71e9cab2 Windows_UI_Xaml!DirectUI::FrameworkView::Run+0xc
    04b1fa74 71e9cab2 009ead50 00000000 00000000 twinapi!Windows::ApplicationModel::Core::CoreApplicationView::Run+0x27
    04b1fa94 71e9c9f6 00000000 04b1fb18 73d25a10 twinapi!`Windows::ApplicationModel::Core::CoreApplicationViewAgileContainer::RuntimeClassInitialize'::`55'::<lambda_A2234BA2CCD64E2C>::operator()+0xb2
    04b1faa0 73d25a10 009ea118 00000000 00000000 twinapi!`Windows::ApplicationModel::Core::CoreApplicationViewAgileContainer::RuntimeClassInitialize'::`55'::<lambda_A2234BA2CCD64E2C>::<helper_func>+0xe
    04b1fb18 765f8543 80004005 04b1fb68 76f9ac69 SHCore!SHWaitForThreadWithWakeMask+0x13b
    04b1fb24 76f9ac69 0083f77c 48ef5d6d 00000000 kernel32!BaseThreadInitThunk+0xe
    04b1fb68 76f9ac3c 73d25931 0083f77c ffffffff ntdll!__RtlUserThreadStart+0x72
    04b1fb80 00000000 73d25931 0083f77c 00000000 ntdll!_RtlUserThreadStart+0x1b


    FOLLOWUP_IP:
    twinapi!Windows::ApplicationModel::Core::CoreApplicationView::SuspendResume+1da [d:\win8_gdr\shell\coreapplication\application\lib\coreapplicationview.cpp @ 944]
    71eb5d08 8b7510          mov     esi,dword ptr [ebp+10h]

    FAULTING_SOURCE_LINE:  d:\win8_gdr\shell\coreapplication\application\lib\coreapplicationview.cpp

    FAULTING_SOURCE_FILE:  d:\win8_gdr\shell\coreapplication\application\lib\coreapplicationview.cpp

    FAULTING_SOURCE_LINE_NUMBER:  944

    SYMBOL_STACK_INDEX:  9

    SYMBOL_NAME:  twinapi!Windows::ApplicationModel::Core::CoreApplicationView::SuspendResume+1da

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: twinapi

    IMAGE_NAME:  twinapi.dll

    DEBUG_FLR_IMAGE_TIMESTAMP:  505a93c3

    STACK_COMMAND:  ~2s ; kb

    BUCKET_ID:  HANG_twinapi!Windows::ApplicationModel::Core::CoreApplicationView::SuspendResume+1da

    FAILURE_BUCKET_ID:  APPLICATION_HANG_cfffffff_twinapi.dll!Windows::ApplicationModel::Core::CoreApplicationView::SuspendResume

    WATSON_STAGEONE_URL:  http://watson.microsoft.com/00000000.htm?Retriage=1

    Followup: MachineOwner
    ---------

     There is no my code on the stack.

    Please explain what it could mean and how I can solve the problem.

    Monday, May 13, 2013 9:17 AM

Answers

  • Hello,

    Your app isn't crashing it is being forcefully shutdown by the framework. The framework is detecting that your application is taking too long to return from suspend or resume and shutting you down. This is expected behavior. This is very common and usually occurs when you are reloading state from a network location. You should be able to create a background task to load the data and not block the suspend or resume thread for an extended period of time.

    I hope this helps,

    James


    Windows SDK Technologies - Microsoft Developer Services - http://blogs.msdn.com/mediasdkstuff/

    Monday, May 13, 2013 8:59 PM
    Moderator
  • Hello,

    The stack information is not useful here. The framework is shutting down your app at the point the stack was collected. The thread running your code has likely already been killed. What you see on the stack at this point is Windows doing housekeeping so that the error is logged correctly. This is expected behavior.

    I hope this helps,

    James


    Windows SDK Technologies - Microsoft Developer Services - http://blogs.msdn.com/mediasdkstuff/

    • Marked as answer by Яков Sunday, May 19, 2013 10:52 AM
    Tuesday, May 14, 2013 10:46 PM
    Moderator

All replies

  • Hello,

    Your app isn't crashing it is being forcefully shutdown by the framework. The framework is detecting that your application is taking too long to return from suspend or resume and shutting you down. This is expected behavior. This is very common and usually occurs when you are reloading state from a network location. You should be able to create a background task to load the data and not block the suspend or resume thread for an extended period of time.

    I hope this helps,

    James


    Windows SDK Technologies - Microsoft Developer Services - http://blogs.msdn.com/mediasdkstuff/

    Monday, May 13, 2013 8:59 PM
    Moderator
  • Thank you for info. But I would like to know more to resolve the issue. Given the stack and other info I posted,what does the framework expect from the application in this case? There are no threads in the process that execute my code.

    Tuesday, May 14, 2013 9:01 AM
  • Hello,

    The stack information is not useful here. The framework is shutting down your app at the point the stack was collected. The thread running your code has likely already been killed. What you see on the stack at this point is Windows doing housekeeping so that the error is logged correctly. This is expected behavior.

    I hope this helps,

    James


    Windows SDK Technologies - Microsoft Developer Services - http://blogs.msdn.com/mediasdkstuff/

    • Marked as answer by Яков Sunday, May 19, 2013 10:52 AM
    Tuesday, May 14, 2013 10:46 PM
    Moderator
  • Thank you for info.

    Sunday, May 19, 2013 10:52 AM