crash dumps - Strange stack trace in Windows Phone 8 -

crash dumps - Strange stack trace in Windows Phone 8 -

hi have windows phone app getting number of crashes reported dev center. did upgrade included minor changes , moving of mutual code silverlight class library windows phone class library (so open project in vs2013). no issues in testing in emulator , on phone.

a fair number of crashes seem in background agent generating tile.. not obvious why can @ to the lowest degree see method in code (not sure how utilize offet find exact line.

however mass of me errors error e06d7363 errors next stack trace. (have cut down ist big include fully) nil in here remotely looks code have no thought start.

any ideas pint me in right direction?

thanks.

frame image function offset 0 headlesshost __imagebase 0x00000007 1 coreclr clrexception::handlerstate::setupcatch 0x00000075 2 coreclr module::doinit 0x00000275 3 msvcrt __cxxcallcatchblock 0x00000077 4 msvcrt _getpid 0x00000608 5 coreclr __dyn_tls_init_callback _perf_ 0x00000000 6 coreclr cassemblylocation::`vftable' 0x0007aa44 7 coreclr cassemblylocation::`vftable' 0x0007aa1c 8 coreclr module::doinit 0x00000133 9 coreclr module::doinit 0x00000001 10 msvcrt __piob _perf_ 0x00000000 11 ntdll __pchsym_ _perf_ 0x00000000 12 coreclr sstring::converttounicode 0x0000002d 13 coreclr module::doinit 0x00000131 14 msvcrt _callsettingframe 0x00000011 15 msvcrt __cxxcallcatchblock 0x000000b1 16 ntdll rcconsolidateframes 0x00000005 17 ntdll rtlunwindex 0x000001d3 18 coreclr operator new 0x00000011 19 coreclr peimage::s_hashlock 0x00000000 20 coreclr peimage::release 0x00000091 21 coreclr binder_space::assemblybinder::bindtosystemsatellite 0x000000d1 22 ntdll rtlunwindex 0x00000001 23 msvcrt _unwindnestedframes 0x00000069 24 msvcrt __cxxcallcatchblock 0x00000001 25 coreclr cassemblylocation::`vftable' 0x0007aa30 26 coreclr cassemblylocation::`vftable' 0x0007aa08 27 msvcrt findhandler 0x0000026f 28 coreclr module::doinit 0x0000011b 29 coreclr cta2pavexception 0x00000008 30 msvcrt _getptd_noexit 0x0000001b 31 msvcrt __internalcxxframehandler 0x00000155 32 msvcrt __cxxframehandler3 0x00000043 33 coreclr cassemblylocation::`vftable' 0x0007ab00 34 ntdll rtlpexecutehandlerforexception 0x00000009 35 ntdll rtldispatchexception 0x0000015d 36 coreclr _cxxframehandler3 0x00000001 37 coreclr exceptionhijack_xdata_end 0x0001b3ec 38 coreclr loaderheap::realallocmemunsafe 0x00000001 39 kernelbase __imagebase 0x00000000 40 kernelbase __pchsym_ _perf_ 0x00000000 41 msvcrt __sbh_initialized 0x00000000 42 msvcrt __piob _perf_ 0x00000000 43 coreclr __dyn_tls_init_callback _perf_ 0x00000000 44 coreclr __dyn_tls_init_callback _perf_ 0x00000000 45 coreclr __dyn_tls_init_callback _perf_ 0x00000000 46 coreclr __dyn_tls_init_callback _perf_ 0x00000000 47 coreclr __dyn_tls_init_callback _perf_ 0x00000000 48 sechost lsalook__midl_typeformatstring 0x000001e2 49 rpcrt4 ndrconformantvaryingarrayunmarshall 0x00000045 <output removed here > 96 coreclr baseassemblyspec::clonefields 0x00000047 97 coreclr __clrallocinprocessheap 0x00000000 98 coreclr eeheapallocinprocessheap

in case finding solution needed lots of surfing through sites , search description of error codes , find solution or can analyze crash reports. you’ll receive certification study contains additional files can utilize identify happened. depending on type of error occurred, you’ll receive either crash dump file or errorinfo file. examine these files, dev centre recommend utilize either microsoft visual studio or windows debugger tools. have on here analyzing crash reports , improving apps quality reports. hope help out.

windows-phone-8 crash-dumps