Submit My Question - Recent Questions - Recent Answer

Msdn Tech >> .NET Development >> Common Language Runtime

IoCompletion handle

Hi.

I'm not sure this is a right topic for that section. I have a problem with growing number of IOCompletion Threads. In our producion environment we have from time to time ExecutionEngineException. I was trying to understand what is going on and started from analysing DUMP file. I found that there are more than 1000 thread doing IOCompletion operation:

103 76 528 084fe878 880b220 Enabled 00000000:00000000 0014d518 0 MTA (Threadpool Completion Port)

the stack of the each of them is:

0:044> ~103e k
ChildEBP RetAddr
0e4af0f8 7c90e31b ntdll!KiFastSystemCallRet
0e4af0fc 7c80a746 ntdll!ZwRemoveIoCompletion+0xc
0e4af128 79f2f30a KERNEL32!GetQueuedCompletionStatus+0x29
0e4af194 79ecb00b mscorwks!ThreadpoolMgr::CompletionPortThreadStart+0x11c
0e4affb4 7c80b683 mscorwks!Thread::intermediateThreadProc+0x49
0e4affec 00000000 KERNEL32!BaseThreadStart+0x37

And all of them deal with handle 000000170

0e4af128 79f2f30a 00000170 0e4af16c 0e4af168 KERNEL32!GetQueuedCompletionStatus+0x29

this is IOCompletion handle:

0:044> !handle 170 ff
Handle 170
Type IoCompletion
Attributes 0
GrantedAccess 0x1f0003:
Delete,ReadControl,WriteDac,WriteOwner,Synch
Query,Modify
HandleCount 2
PointerCount 9
Name <none>
Object Specific Information
Depth 0

Could any body help me to get more information about that handle? I guess it is linked to Socket operation (.NEt Remoting probably) But I'm not sure. I was tring to debug in kernel mode and what I got is:

lkd> !handle 170 ff 88d36be8
processor number 0, process 88d36be8
PROCESS 88d36be8 SessionId: 0 Cid: 0b70 Peb: 7ffdf000 ParentCid: 02e8
DirBase: 0a540400 ObjectTable: e2b3d348 HandleCount: 2604.
Image: BatchService.exe

Kernel Handle table at e23f9000 with 1170 Entries in use
0170: Object: 88298ae0 GrantedAccess: 0012019f Entry: e10042e0
Object: 88298ae0 Type: (0a130014)
ObjectHeader: 88298ac8
HandleCount: 0 PointerCount: 0
Directory Object: 8a808829 Name: (*** Name not accessible ***)

Any suggestions?

[2655 byte] By [EvgenyPopov] at [2007-12-24]

«« Images in DatagridView
»» Learning C#

# 1

Why is the handle count in the kernel mode debug 0? You said you were looking at a hang mode dump file. How did you get the active process address in kernel mode? Are you looking at the right process?

Remember that handles are process specific. This value, "170h", was only known within the process that you took the hang mode dump from. Kernel mode debug will give you active processes on the box you are running WinDBG on. If this handle value was sent to another process (which could be an instance of the same process that you are debugging), it would either not exist or most likely be a handle to a different object. IOCompletion handles are not like window handles, their scope is within a process.

NikhilRajwade at 2007-8-31 >

top of Msdn Tech,.NET Development,Common Language Runtime...

# 2

Hi Nikhil,

Thank you for answer. I was analysing DUMP file. But it was not enough information there so I started the same process in kernal mode on my box and got this active address. I understand that the handle could be different and it is just hit for me. Because the process goes the same way evry time and handle changes his address but based on stack and code I can identify the "same" object by a moment when it's created and how is it used. It means that I use real process and kernel mode to understand what is behind that handle. Every time I run those process I got similar picture. But I understand that I could go the wrong way. But I just don't know any others way. The main question why the number of the IOCompletion thread is going up? Probly if I have kernel level dump file it will help me.

Eugene

EvgenyPopov at 2007-8-31 >

# 3

Ok, if the kernel mode handle information is 'real' then I dont think you are going to get any more information about the IOCompletion handle. The number of IOCompletion threads is going up because you have queued IO. Also those threads are simply waiting for an IO call to finish. You need to find the source.

I would suggest that you try and find other threads that are trying to start IO work, eg: Remoting calls/webservice calls.. Look at all your managed threads (Infact ignore the IOCompletion threads). Use Lutz Roeders Reflector tool to reverse engineer the assembly and read the code. If you have 1000 IOCompletion threads the IO work in the application is going to be quite apparent and probably a major part of the application.

The last time I saw a similar problem was in a managed windows service application that one of our guys wrote that was making web service calls. The max http request limit was set the default of 2, which meant that multithreaded webservice calls were being queued up. As a result the application eventually ran out of IOThreads (this was on 1.1 where it wasnt easy to change the threadpool size with a default of 25). Increasing the max http requests in machine.config solved the problem.

So in a nutshell, the problem that you have 1000 IO completion threads is a false positive. You need to look at the other managed threads to find out whats creating them.

NikhilRajwade at 2007-8-31 >

# 4

I was trying to reproduce this problem. If I understand you correctly I just need to create test which runs a lot of threads on methods which does Web Service call. This is my code:

public override void Start()

{

try

{

for (int i = 0; i < 100; i++)

{

ThreadPool.QueueUserWorkItem(new WaitCallback(Do));

}

Thread.Sleep(100000);

}

catch(Exception ex)

{

System.Diagnostics.Debug.WriteLine(ex.ToString());

}

private void Do(object param)

{

TestWebService.Service1 service = new BatchProcessExample.TestWebService.Service1();

service.HelloWorld();

}

This code does not generate more than one IOCompletion thread. Where I'm wrong?

EvgenyPopov at 2007-8-31 >

# 5

This webpage looks useful. Be sure to always match a BeginXxxx() with an EndXxxx() call.

nobugz at 2007-8-31 >

# 6

Thank you nobugz for the article. It was interesting but didn't really help me. Moving forward, I found that in my DUMP file there are 1478 System.LazyAsyncResult+ThreadContext objects. ThreadContext is a private class defined inside System.LazyAsyncResult, it means that it could be created only by System.LazyAsyncResult instance. But there is no such instances in memory. I'm not sure it signals something wrong, but for me it seams it. Probably, thread was terminated but IO operation was not completed and references are still alive. And I have no idea where does those objects come from, because we have .Net Remoting, Web Service calls, sending e-mail, db connections, file operations. And it is really hard to iluminate base on a code where problem is.

The next interesting I have found, all !threadpool returns this:

Completion Port Thread:Total: 1738 Free: 1738 MaxFree: 8 CurrentLimit: 1000 MaxLimit: 1000 MinLimit: 4
Why total completion thread number more than 1000? And As I understand, all those threads started running at some time and each second the new one was created.

Have anybody had behaivor like this?

How can I understand based on System.Thread object address what thread created this object?

EvgenyPopov at 2007-8-31 >

# 7

I am a little confused now. What exactly are you trying to find? if you are looking for the thread that caused the exception you should be able to see that through !threads . if you took the dump in crash mode you should actually start in the thread that caused the exception. You can look at managed thread stack using !clrstack or !eestack . If you are looking for the source of the IOCompletions you should look at threads that may be involved in some async IO. You can read code either using !dumpil or a cool tool like Lutz Roeders Reflector.

There is no point in blindly going around a dump file looking for problems. Almost everything looks like a problem there. You need to have some understanding of the application behaviour in order to effectively debug applications in production. It is quite normal to see high amount of IOCompletion if you are doing partial read/writes. You can avoid that by calling EndResult on the AsyncResult object in the callback.

Can you put the exception and or the eestack here? Maybe we can help you better then.

Regards,

Nikhil

NikhilRajwade at 2007-8-31 >

# 8

Sorry for confusing. I was confused too. Actually the dump I analysed is not a crash dump. I 'm not able to get crash dump because all real work are performed in separate domains and separate threads, and when crash is happened all those threads are terminated and dump file contains only main thread. It was the reason of analysing DUMP file that is made before crash when the number of the thread is high. And the dump file does not contain any managed thread, so I was not able to guess where do those threads come from. But yesterday I captured performance counters from production and released that the number of the threads goes up and down, periodically. And I released that I need a dump file in the middle of that process to find managed thread which generates all of them. And we have done it!!! I got dump file in the middle of the threads growing. And I found what I was looking for. This is a unmanaged stack of that thread:

0:020> kb
ChildEBP RetAddr Args to Child
4dccd064 7c821c94 77c72700 00002af8 0c8f78f0 ntdll!KiFastSystemCallRet
4dccd068 77c72700 00002af8 0c8f78f0 0c8f78f0 ntdll!NtRequestWaitReplyPort+0xc
4dccd0b4 77c713ba 03b0af6c 4dccd0dc 77788056 rpcrt4!LRPC_CCALL::SendReceive+0x230
4dccd0c0 77788056 03b0af6c 4dccd1c0 0c5ab554 rpcrt4!I_RpcSendReceive+0x24
4dccd0dc 77788011 00000000 00000000 00000000 ole32!ThreadSendReceive+0xf5
4dccd0f8 77787ed7 4dccd1c0 4dccd2c0 03b5c138 ole32!CRpcChannelBuffer::SwitchAptAndDispatchCall+0x112
4dccd1d8 77695349 03b5c138 4dccd2d0 4dccd2c0 ole32!CRpcChannelBuffer::SendReceive2+0xc1
4dccd244 776c4eee 03b5c138 4dccd2d0 4dccd2c0 ole32!CAptRpcChnl::SendReceive+0xab
4dccd298 77ce127e 00000001 4dccd2d0 4dccd2c0 ole32!CCtxComChnl::SendReceive+0x91
4dccd2b4 77ce13ca 03be0964 4dccd2fc 0300002c rpcrt4!NdrProxySendReceive+0x43
4dccd69c 77ce11bd 0c7fd200 0c7feaa4 4dccd6d4 rpcrt4!NdrClientCall2+0x206
4dccd6bc 77c53a12 0000000c 00000097 4dccd714 rpcrt4!ObjectStublessClient+0x8b
4dccd74c 79f32572 d7c84753 00000000 00000003 rpcrt4!ObjectStubless+0xf
4dccd714 06684d6f 01137ff0 01141bc0 4dccd968 mscorwks!JIT_LDiv+0x6f
WARNING: Frame IP not in any known module. Following frames may be wrong.
4dccd768 06684164 010beed8 010cf48c 00000006 0x6684d6f
4dccd990 057a09b4 d7c84753 88c8b0fb 010cf4d8 0x6684164
4dccda00 057a029a 00000000 00002bc3 00000000 0x57a09b4
4dccda04 00000000 00002bc3 00000000 00000000 0x57a029a

This is a part of the managed stack:

4dccd72c 7c82ed54 [ComPlusMethodFrameStandaloneCleanup: 4dccd72c] ValueEng.Product_CalculatorClass.CalculateValue()
.............
4dccdb18 03ff0e3f Chatham.PandA.CapVols.CapVolCalibration.Start()

So we deal with COM+ communication. The only one thing I can understand what is a preconditions of such behaivor? How Can I reproduce this behaivor on test environment? And is it normal or abnormal? Why .NET starting creates a lot of IOCompletion threads in my case? Why all those threads are running in default app domain? Is it because this code is belong to mscorlib.dll ad that library is loaded always in default app domain?

Eugene.

EvgenyPopov at 2007-8-31 >

# 9

The bad thing here is ADODB.Connection object is passed to COM+ application. I don't like it, I'm I right that all DB operations based on this connection goes as out-proc calls? Could it be the reason of those IOCompletion threads?

Eugene

EvgenyPopov at 2007-8-31 >

# 10

Is the Com component running out of process? Probably not if you are able to see the managed thread call stack (presumably from the COM component) in the debug. So the connections are not out of process. You need to take a dump of the process in crash mode instead of hang mode. I.e. set Adplus to take a memory dump with the -crash option when an exception occurs. That will give you the thread that caused the exception and state of memory/application at that time. Ignore the fact that you have high amount of IOCompletion threads. This could be normal behaviour or could be a problem. However nothing you have mentioned so far indicates that this is a problem. Try locate the thread and cause of exception first. see http://support.microsoft.com/kb/286350/ for more info on crash mode. It doesnt matter what domain/thread this exception occurs on.

next time dump out the !clrstack with the native callstack of a managed thread.

Hope this helps!

NikhilRajwade at 2007-8-31 >

# 11

Yes Com component is running out of process. This was a stack of the my process. Thank you for suggestion to use Adplus, I hope than behaivor of Adplus is deferent from tool what I used for crash dump. I defenatly will try to set it up tomorrow and get crash dump file. But now I have two independed problem: failure and io threads. I will have more information about failure tomorrow but I have everything for iothreads problem if it is problem... In the last message I sent stack of the managed thread which generates IO threads. As you asked I'm sending the full stack:

This is a stack of Worker Thread:

Thread 170

Current frame: ntdll!KiFastSystemCallRet

ChildEBP RetAddrCaller,Callee

12f7fd08 7c822124 ntdll!NtWaitForSingleObject+0xc

12f7fd0c 77e6baa8 kernel32!WaitForSingleObjectEx+0xac, calling ntdll!ZwWaitForSingleObject

12f7fd7c 79e77fd1 mscorwks!PEImage::LoadImage+0x199

12f7fdc0 79e77f9a mscorwks!CLREvent::WaitEx+0x117, calling mscorwks!PEImage::LoadImage+0x16a

12f7fde0 7a07bc1f mscorwks!Holder<Thread *,&DoNothing<Thread *>,&ResetThreadSecurityState,0,&CompareDefault<Thread *>,2>::~Holder<Thread *,&DoNothing<Thread *>,&ResetThreadSecurityState,0,&CompareDefault<Thread *>,2>+0x2b, calling mscorwks!_EH_epilog3

12f7fe10 79e77f50 mscorwks!CLREvent::Wait+0x17, calling mscorwks!CLREvent::WaitEx

12f7fe20 79f5b69c mscorwks!ThreadpoolMgr::SafeWait+0x73, calling mscorwks!CLREvent::Wait

12f7fe70 79f7b3be mscorwks!Thread::InternalReset+0x128, calling mscorwks!_EH_epilog3

12f7fea0 7a1121c3 mscorwks!ThreadpoolMgr::WorkerThreadStart+0xf1, calling mscorwks!ThreadpoolMgr::SafeWait

12f7fed0 79e7839d mscorwks!EEHeapFreeInProcessHeap+0x21, calling mscorwks!EEHeapFree

12f7fee0 79e782dc mscorwks!operator delete[]+0x30, calling mscorwks!EEHeapFreeInProcessHeap

12f7ff14 79ecb00b mscorwks!Thread::intermediateThreadProc+0x49

12f7ffa4 79ecaff9 mscorwks!Thread::intermediateThreadProc+0x37, calling mscorwks!_alloca_probe_16

12f7ffb8 77e66063 kernel32!BaseThreadStart+0x34

This is a stack of IOCompletion thread, most of them contains the same stack.

Thread 731

Current frame: ntdll!KiFastSystemCallRet

ChildEBP RetAddrCaller,Callee

38baeef8 7c821bf4 ntdll!NtRemoveIoCompletion+0xc

38baeefc 77e6611a kernel32!GetQueuedCompletionStatus+0x29, calling ntdll!NtRemoveIoCompletion

38baef28 79f2f30a mscorwks!ThreadpoolMgr::CompletionPortThreadStart+0x11c

38baef94 79ecb00b mscorwks!Thread::intermediateThreadProc+0x49

38baf110 7c831fb2 ntdll!RtlImageNtHeaderEx+0xee, calling ntdll!_SEH_epilog

38baf144 7c831fb2 ntdll!RtlImageNtHeaderEx+0xee, calling ntdll!_SEH_epilog

38baf148 7c831fe4 ntdll!RtlImageNtHeader+0x1b, calling ntdll!RtlImageNtHeaderEx

38baf168 77e62b4e kernel32!ConsoleApp+0xe, calling ntdll!RtlImageNtHeader

38baf170 77e62b8f kernel32!ConDllInitialize+0x1f5, calling kernel32!ConsoleApp

38baf178 77e62ba4 kernel32!ConDllInitialize+0x20a, calling kernel32!__security_check_cookie

38baf2a4 7c83a930 ntdll!bsearch+0x42

38baf2b4 7c83a930 ntdll!bsearch+0x42

38baf2c0 7c83a878 ntdll!ARRAY_FITS+0x29, calling ntdll!ULongAdd

38baf2d4 7c83a78f ntdll!RtlpLocateActivationContextSection+0x1da, calling ntdll!ARRAY_FITS

38baf304 7c83aa25 ntdll!RtlpFindUnicodeStringInSection+0x7b, calling ntdll!RtlHashUnicodeString

38baf314 7c83a615 ntdll!RtlpFindNextActivationContextSection+0x64, calling ntdll!RtlpLocateActivationContextSection

38baf344 7c83ab9e ntdll!RtlFindNextActivationContextSection+0x46, calling ntdll!RtlpFindNextActivationContextSection

38baf364 7c832d06 ntdll!RtlFindActivationContextSectionString+0xe1, calling ntdll!RtlFindNextActivationContextSection

38baf3b0 7c8330db ntdll!RtlEncodeSystemPointer+0xa09, calling ntdll!RtlFindActivationContextSectionString

38baf3cc 7c833139 ntdll!RtlEncodeSystemPointer+0xb25, calling ntdll!__security_check_cookie

38baf444 7c833180 ntdll!RtlEncodeSystemPointer+0x46b, calling ntdll!RtlFindCharInUnicodeString

38baf47c 7c832f80 ntdll!RtlDosApplyFileIsolationRedirection_Ustr+0x346, calling ntdll!RtlFreeAnsiString

38baf48c 7c832fe5 ntdll!RtlDosApplyFileIsolationRedirection_Ustr+0x3de, calling ntdll!__security_check_cookie

38baf5a8 7c832b78 ntdll!LdrUnlockLoaderLock+0x84, calling ntdll!RtlLeaveCriticalSection

38baf5ac 7c832b7f ntdll!LdrUnlockLoaderLock+0xad, calling ntdll!_SEH_epilog

38baf5c0 7c832b78 ntdll!LdrUnlockLoaderLock+0x84, calling ntdll!RtlLeaveCriticalSection

38baf5c4 7c832b7f ntdll!LdrUnlockLoaderLock+0xad, calling ntdll!_SEH_epilog

38baf5dc 7c836c4d ntdll!LdrGetDllHandleEx+0xbe, calling ntdll!RtlDosApplyFileIsolationRedirection_Ustr

38baf5f0 7c832b7f ntdll!LdrUnlockLoaderLock+0xad, calling ntdll!_SEH_epilog

38baf5f4 7c836b93 ntdll!LdrGetDllHandleEx+0x368, calling ntdll!LdrUnlockLoaderLock

38baf600 7c836b56 ntdll!LdrGetDllHandleEx+0x329, calling ntdll!_SEH_epilog

38baf628 7c836b56 ntdll!LdrGetDllHandleEx+0x329, calling ntdll!_SEH_epilog

38baf658 7c836cf9 ntdll!LdrGetDllHandle+0x18, calling ntdll!LdrGetDllHandleEx

38baf66c 7c836b56 ntdll!LdrGetDllHandleEx+0x329, calling ntdll!_SEH_epilog

38baf670 7c836cf9 ntdll!LdrGetDllHandle+0x18, calling ntdll!LdrGetDllHandleEx

38baf68c 77e665bb kernel32!GetModuleHandleForUnicodeString+0x20

38baf69c 77e665cb kernel32!GetModuleHandleForUnicodeString+0x97, calling kernel32!_SEH_epilog

38baf6b4 77e665bb kernel32!GetModuleHandleForUnicodeString+0x20

38baf6d4 77e665cb kernel32!GetModuleHandleForUnicodeString+0x97, calling kernel32!_SEH_epilog

38baf6d8 77e664ee kernel32!BasepGetModuleHandleExW+0x17f, calling kernel32!GetModuleHandleForUnicodeString

38baf6dc 77e6656e kernel32!BasepGetModuleHandleExW+0x23c, calling kernel32!_SEH_epilog

38baf7c0 77e65f41 kernel32!_BaseDllInitialize+0x6b, calling kernel32!ConDllInitialize

38baf7d0 77e65f55 kernel32!_BaseDllInitialize+0x430, calling kernel32!__security_check_cookie

38baf8b4 7c8302e7 ntdll!RtlpAllocateFromHeapLookaside+0x13, calling ntdll!ExInterlockedPopEntrySList

38baf8cc 772c1b8a urlmon!EnsureFeatureCache+0x56, calling kernel32!TlsSetValue

38baf8d8 772c1744 urlmon!EnsureFeatureCache+0x33e, calling urlmon!__security_check_cookie

38baf8fc 7c8339a3 ntdll!LdrpSnapThunk+0xc0, calling ntdll!LdrpNameToOrdinal

38baf928 7c82fda6 ntdll!RtlAllocateHeap+0x460, calling ntdll!RtlLeaveCriticalSection

38baf92c 7c82fb23 ntdll!RtlAllocateHeap+0xee7, calling ntdll!_SEH_epilog

38baf944 7c82fda6 ntdll!RtlAllocateHeap+0x460, calling ntdll!RtlLeaveCriticalSection

38baf948 7c82fb23 ntdll!RtlAllocateHeap+0xee7, calling ntdll!_SEH_epilog

38baf964 7c833ae4 ntdll!LdrpGetProcedureAddress+0x189, calling ntdll!LdrpSnapThunk

38baf97c 7c82fda6 ntdll!RtlAllocateHeap+0x460, calling ntdll!RtlLeaveCriticalSection

38baf980 7c82fb23 ntdll!RtlAllocateHeap+0xee7, calling ntdll!_SEH_epilog

38bafa1c 7c833b1c ntdll!LdrpGetProcedureAddress+0xb3, calling ntdll!_SEH_epilog

38bafa4c 7c831fb2 ntdll!RtlImageNtHeaderEx+0xee, calling ntdll!_SEH_epilog

38bafa88 7c8379db ntdll!LdrpGetProcedureAddress+0x274, calling ntdll!RtlLeaveCriticalSection

38bafa98 77d0404b oleaut32!DllMain+0x2c, calling oleaut32!_typesDllMain

38bafab0 77d0407c oleaut32!DllMain+0x203, calling oleaut32!__security_check_cookie

38bafaec 772c1a9c urlmon!CUrlMkTls::TLSAllocData+0x3c, calling kernel32!TlsSetValue

38bafb00 772c1a4d urlmon!CUrlMkTls::CUrlMkTls+0x29, calling urlmon!CUrlMkTls::TLSAllocData

38bafb0c 772c1935 urlmon!TlsDllMain+0xf2, calling urlmon!EnsureFeatureCache

38bafb68 7c82fb23 ntdll!RtlAllocateHeap+0xee7, calling ntdll!_SEH_epilog

38bafb6c 764d6844 msoert2!calloc+0xa9, calling ntdll!RtlAllocateHeap

38bafb78 764d6879 msoert2!calloc+0xde, calling msoert2!_SEH_epilog

38bafb88 77e660d6 kernel32!FlsSetValue+0xc7, calling kernel32!_SEH_epilog

38bafb98 76dc13df adsldpc!LibMain+0x20a, calling adsldpc!_SEH_epilog

38bafbdc 73ca13f1 cryptnet!_DllMainCRTStartup+0x52, calling cryptnet!DllMain

38bafbfc 7c82257a ntdll!LdrpCallInitRoutine+0x14

38bafc24 7c81a81b ntdll!LdrpInitializeThread+0x1a5, calling ntdll!RtlLeaveCriticalSection

38bafc2c 7c81b26f ntdll!LdrpInitializeThread+0x18f, calling ntdll!_SEH_epilog

38bafc7c 7c81a7dc ntdll!LdrpInitializeThread+0xd8, calling ntdll!RtlActivateActivationContextUnsafeFast

38bafc80 7c81a7a4 ntdll!LdrpInitializeThread+0x12c, calling ntdll!RtlDeactivateActivationContextUnsafeFast

38bafcb4 7c81b26f ntdll!LdrpInitializeThread+0x18f, calling ntdll!_SEH_epilog

38bafcb8 7c822054 ntdll!ZwTestAlert+0xc

38bafcbc 7c81b23f ntdll!_LdrpInitialize+0x1de, calling ntdll!_SEH_epilog

38bafd10 7c81b23f ntdll!_LdrpInitialize+0x1de, calling ntdll!_SEH_epilog

38bafd14 7c8211b4 ntdll!ZwContinue+0xc

38bafd18 7c82ec42 ntdll!KiUserApcDispatcher+0x3a, calling ntdll!NtContinue

38baffa4 79ecaff9 mscorwks!Thread::intermediateThreadProc+0x37, calling mscorwks!_alloca_probe_16

38baffb8 77e66063 kernel32!BaseThreadStart+0x34

This is a stack of second managed thread, this thread is doing some real work:

Thread 727

Current frame: mscorjit!Compiler::gtNewNode+0x2d

ChildEBP RetAddrCaller,Callee

337fc298 7906599f mscorjit!Compiler::gtNewOperNode+0x9, calling mscorjit!Compiler::gtNewNode

337fc2a0 790a48dd mscorjit!Compiler::impImportBlockCode+0x19cd, calling mscorjit!Compiler::gtNewOperNode

337fc310 7c8302e7 ntdll!RtlpAllocateFromHeapLookaside+0x13, calling ntdll!ExInterlockedPopEntrySList

337fc31c 7c82fadf ntdll!RtlAllocateHeap+0x1dd, calling ntdll!RtlpAllocateFromHeapLookaside

337fc320 7c82fb23 ntdll!RtlAllocateHeap+0xee7, calling ntdll!_SEH_epilog

337fc348 7c8302e7 ntdll!RtlpAllocateFromHeapLookaside+0x13, calling ntdll!ExInterlockedPopEntrySList

337fc358 7c82fb23 ntdll!RtlAllocateHeap+0xee7, calling ntdll!_SEH_epilog

337fc374 79e7d9b5 mscorwks!TypeSecurityDescriptor::ComputeTypeDeclarativeSecurityInfo+0xab, calling mscorwks!_EH_epilog3

337fc3a0 79e7d9b5 mscorwks!TypeSecurityDescriptor::ComputeTypeDeclarativeSecurityInfo+0xab, calling mscorwks!_EH_epilog3

337fc3f4 79e7da05 mscorwks!TypeSecurityDescriptor::ComputeCriticalTransparentInfo+0x36, calling mscorwks!ModuleSecurityDescriptor::VerifyDataComputed

337fc40c 79e7d9b5 mscorwks!TypeSecurityDescriptor::ComputeTypeDeclarativeSecurityInfo+0xab, calling mscorwks!_EH_epilog3

337fc410 79e7d986 mscorwks!TypeSecurityDescriptor::VerifyDataComputedInternal+0x21, calling mscorwks!TypeSecurityDescriptor::ComputeTypeDeclarativeSecurityInfo

337fc418 79e7d92e mscorwks!MethodSecurityDescriptor::ComputeCriticalTransparentInfo+0x35, calling mscorwks!TypeSecurityDescriptor::VerifyDataComputed

337fc438 79e7d9b5 mscorwks!TypeSecurityDescriptor::ComputeTypeDeclarativeSecurityInfo+0xab, calling mscorwks!_EH_epilog3

337fc43c 79e7d986 mscorwks!TypeSecurityDescriptor::VerifyDataComputedInternal+0x21, calling mscorwks!TypeSecurityDescriptor::ComputeTypeDeclarativeSecurityInfo

337fc444 79e7d92e mscorwks!MethodSecurityDescriptor::ComputeCriticalTransparentInfo+0x35, calling mscorwks!TypeSecurityDescriptor::VerifyDataComputed

337fc494 79e7dadc mscorwks!SecurityTransparent::IsMethodTransparent+0x27, calling mscorwks!MethodSecurityDescriptor::VerifyDataComputed

337fc4c4 79e98611 mscorwks!ClassLoader::CanAccessMemberForExtraChecks+0x11, calling mscorwks!SecurityTransparent::IsMethodTransparent

337fc4d4 79e9853c mscorwks!ClassLoader::CanAccess+0x94, calling mscorwks!ClassLoader::CanAccessMemberForExtraChecks

337fc4f8 79e9aea9 mscorwks!CEEInfo::findFieldInternal+0x238, calling mscorwks!ClassLoader::CanAccess

337fc514 79e9af08 mscorwks!FieldDesc::IsNonVerifiableExplicitField+0x5, calling mscorwks!FieldDesc::GetEnclosingMethodTable

337fc518 79e9aedc mscorwks!CEEInfo::findFieldInternal+0x2e4, calling mscorwks!GCFrame::Pop

337fc528 79e9aef9 mscorwks!CEEInfo::findFieldInternal+0x301, calling mscorwks!__security_check_cookie

337fc558 79e74435 mscorwks!DecCantStopCount+0x10, calling mscorwks!ClrFlsSetValue

337fc5a8 79e7a5dd mscorwks!Holder<void *,&ClrEnterCriticalSection,&ClrLeaveCriticalSection,0,&CompareDefault<void *>,2>::~Holder<void *,&ClrEnterCriticalSection,&ClrLeaveCriticalSection,0,&CompareDefault<void *>,2>+0x22, calling mscorwks!ClrLeaveCriticalSection

337fc5b8 79e783e6 mscorwks!EEHeapFree+0xa5, calling mscorwks!_EH_epilog3

337fc5bc 79e7839d mscorwks!EEHeapFreeInProcessHeap+0x21, calling mscorwks!EEHeapFree

337fc5d8 7c8302b3 ntdll!RtlpFreeToHeapLookaside+0x22, calling ntdll!RtlpInterlockedPushEntrySList

337fc5e4 7c82f9c1 ntdll!RtlFreeHeap+0x20e, calling ntdll!RtlpFreeToHeapLookaside

337fc5ec 7c82f9dd ntdll!RtlFreeHeap+0x70f, calling ntdll!_SEH_epilog

337fc5fc 79e782ed mscorwks!operator delete[]+0x41, calling mscorwks!_EH_epilog3

337fc600 79e7a9ff mscorwks!SArray<MethodDesc *,1>::~SArray<MethodDesc *,1>+0x21, calling mscorwks!operator delete[]

337fc604 79e7a9f6 mscorwks!SArray<MethodDesc *,1>::~SArray<MethodDesc *,1>+0x27, calling mscorwks!_EH_epilog3

337fc61c 79e786aa mscorwks!CLRException::HandlerState::CleanupTry+0x13, calling mscorwks!GetCurrentSEHRecord

337fc62c 79e9c245 mscorwks!EEJitManager::setVars+0x106, calling mscorwks!CLRException::HandlerState::CleanupTry

337fc644 79e9c26a mscorwks!EEJitManager::setVars+0x1e9, calling mscorwks!__security_check_cookie

337fc680 79e98638 mscorwks!FieldDesc::GetExactClassInstantiation+0x24, calling mscorwks!MethodTable::GetInstantiation

337fc684 79e7e4f8 mscorwks!Holder<Frame *,&DoNothing<Frame *>,&COMPlusCooperativeTransitionHandler,0,&CompareDefault<Frame *>,2>::~Holder<Frame *,&DoNothing<Frame *>,&COMPlusCooperativeTransitionHandler,0,&CompareDefault<Frame *>,2>+0x2b, calling mscorwks!_EH_epilog3

337fc6a4 79e7a773 mscorwks!Thread::EnablePreemptiveGC+0xf, calling mscorwks!Thread::CatchAtSafePoint

337fc6ac 79e9aaa1 mscorwks!CEEInfo::getFieldType+0x1e9, calling mscorwks!_EH_epilog3

337fc6ec 79e7c926 mscorwks!ClassLoader::LoadTypeDefOrRefThrowing+0x6d, calling mscorwks!TypeHandle::IsGenericTypeDefinition

337fc730 79e9aaa1 mscorwks!CEEInfo::getFieldType+0x1e9, calling mscorwks!_EH_epilog3

337fc778 79068332 mscorjit!Compiler::impAppendStmt+0xae, calling mscorjit!Compiler::impCurStmtOffsSet

337fc790 79069ebc mscorjit!Compiler::impAppendTree+0x1a, calling mscorjit!Compiler::impAppendStmt

337fc79c 790a7125 mscorjit!Compiler::impImportBlock+0x549, calling mscorjit!Compiler::impAppendTree

337fc7a4 7906f666 mscorjit!Compiler::impImportBlock+0x70d, calling mscorjit!_SEH_epilog4

337fc7c4 79e7c34e mscorwks!CorSigEatCustomModifiers+0x1c, calling mscorwks!CorSigEatAnyVASentinel

337fc7cc 79e7c34e mscorwks!CorSigEatCustomModifiers+0x1c, calling mscorwks!CorSigEatAnyVASentinel

337fc864 7906f5e4 mscorjit!Compiler::impImportBlock+0x20c, calling mscorjit!Compiler::impImportBlockCode

337fc880 7906ccf2 mscorjit!Compiler::fgMakeBasicBlocks+0x3ca, calling mscorjit!Compiler::fgLinkBasicBlocks

337fc8d0 7909d46f mscorjit!Compiler::impRestoreStackState+0x2f, calling msvcr80!memcpy [F:\RTM\vctools\crt_bld\SELF_X86\crt\src\intel\memcpy.asm:101]

337fc8e8 7906f57d mscorjit!Compiler::impImport+0xe3, calling mscorjit!Compiler::impImportBlock

337fc8fc 7906f4b8 mscorjit!Compiler::fgImport+0x20, calling mscorjit!Compiler::impImport

337fc908 7906de9b mscorjit!Compiler::compCompile+0xb, calling mscorjit!Compiler::fgImport

337fc914 7906ebee mscorjit!Compiler::compCompile+0x2d8, calling mscorjit!Compiler::compCompile

337fc96c 7906e8db mscorjit!jitNativeCode+0xb8, calling mscorjit!Compiler::compCompile

337fc9a8 79e7da05 mscorwks!TypeSecurityDescriptor::ComputeCriticalTransparentInfo+0x36, calling mscorwks!ModuleSecurityDescriptor::VerifyDataComputed

337fc9bc 79e7d9b5 mscorwks!TypeSecurityDescriptor::ComputeTypeDeclarativeSecurityInfo+0xab, calling mscorwks!_EH_epilog3

337fca00 7906e831 mscorjit!CILJit::compileMethod+0x3d, calling mscorjit!jitNativeCode

337fca38 79e9776f mscorwks!invokeCompileMethodHelper+0x72

337fcaa4 79e976e5 mscorwks!invokeCompileMethod+0x31, calling mscorwks!invokeCompileMethodHelper

337fcae8 79e9767a mscorwks!CallCompileMethodWithSEHWrapper+0x84, calling mscorwks!invokeCompileMethod

337fcb40 79e97516 mscorwks!UnsafeJitFunction+0x212, calling mscorwks!CallCompileMethodWithSEHWrapper

337fccec 7c8302e7 ntdll!RtlpAllocateFromHeapLookaside+0x13, calling ntdll!ExInterlockedPopEntrySList

337fccf4 7c831fb2 ntdll!RtlImageNtHeaderEx+0xee, calling ntdll!_SEH_epilog

337fcd28 7c831fb2 ntdll!RtlImageNtHeaderEx+0xee, calling ntdll!_SEH_epilog

337fcd2c 7c831fe4 ntdll!RtlImageNtHeader+0x1b, calling ntdll!RtlImageNtHeaderEx

337fcd4c 77e60d53 kernel32!GetProcessVersion+0xf4, calling ntdll!RtlImageNtHeader

337fcd50 77e60d7f kernel32!GetProcessVersion+0x126, calling kernel32!_SEH_epilog

337fcd68 79eebdd4 mscorwks!MethodTable::FindEncodedMapDispatchEntry+0x11a, calling mscorwks!__security_check_cookie

337fcdb8 77e60d7f kernel32!GetProcessVersion+0x126, calling kernel32!_SEH_epilog

337fcdbc 77e60e38 kernel32!GetSystemInfoInternal+0xb4, calling kernel32!GetProcessVersion

337fcdd0 77e60e8d kernel32!GetSystemInfo+0x3f, calling kernel32!GetSystemInfoInternal

337fcdfc 7c8322d8 ntdll!RtlInitializeCriticalSectionAndSpinCount+0xde, calling ntdll!RtlLeaveCriticalSection

337fce18 7c8327cd ntdll!RtlInitializeCriticalSection+0x10, calling ntdll!RtlInitializeCriticalSectionAndSpinCount

337fce28 77e684ee kernel32!InitializeCriticalSection+0xe, calling ntdll!RtlInitializeCriticalSection

337fce34 79e7a501 mscorwks!CrstBase::InitWorker+0x92, calling kernel32!InitializeCriticalSection

337fce38 79e7a521 mscorwks!CrstBase::InitWorker+0xb2, calling mscorwks!_EH_epilog3

337fce54 7c82fb23 ntdll!RtlAllocateHeap+0xee7, calling ntdll!_SEH_epilog

337fce74 79e744a2 mscorwks!UnsafeEELeaveCriticalSection+0xa, calling ntdll!RtlLeaveCriticalSection

337fce78 79e744b5 mscorwks!UnsafeEELeaveCriticalSection+0x1d, calling(JitHelp: CORINFO_HELP_GET_THREAD)

337fce7c 79e7473a mscorwks!CrstBase::Leave+0x77, calling mscorwks!UnsafeEELeaveCriticalSection

337fce80 79e74753 mscorwks!CrstBase::Leave+0x96, calling mscorwks!_EH_epilog3

337fcea0 79e74811 mscorwks!CrstBase::Enter+0xe2, calling ntdll!RtlTryEnterCriticalSection

337fcea4 79e74845 mscorwks!CrstBase::Enter+0x1eb, calling mscorwks!_EH_epilog3

337fced0 79e7adb7 mscorwks!DeadlockAwareLock::EndEnterLock+0x11, calling(JitHelp: CORINFO_HELP_GET_THREAD)

337fced8 79e7adc3 mscorwks!DeadlockAwareLock::ReleaseBlockingLock+0x6, calling(JitHelp: CORINFO_HELP_GET_THREAD)

337fcedc 79e7b9f8 mscorwks!ListLockEntry::FinishDeadlockAwareEnter+0x41, calling mscorwks!_EH_epilog3

337fcef8 79e9731c mscorwks!MethodDesc::MakeJitWorker+0x1c2, calling mscorwks!UnsafeJitFunction

337fcf5c 79e971ba mscorwks!PEFile::CheckIL+0x40, calling mscorwks!PEDecoder::CheckRva

337fcf9c 79e7d58c mscorwks!MethodDesc::DoPrestub+0x44d, calling mscorwks!MethodDesc::MakeJitWorker

337fcff4 79e7bb73 mscorwks!PreStubWorker+0xed, calling mscorwks!MethodDesc::DoPrestub

337fd044 00331efe 00331efe, calling mscorwks!PreStubWorker

337fd05c 07ea5853 (MethodDesc 0x7eba968 +0x183 Aspose.Word.File.a6.a(Aspose.Word.File.b, Aspose.Word.File.y, System.IO.BinaryReader)), calling 03409756

337fd07c 07ea5853 (MethodDesc 0x7eba968 +0x183 Aspose.Word.File.a6.a(Aspose.Word.File.b, Aspose.Word.File.y, System.IO.BinaryReader)), calling 03409756

337fd0c0 07ea558b (MethodDesc 0x7eb2a78 +0x9b Aspose.Word.File.ap.a(Aspose.Word.File.a0)), calling (MethodDesc 0x7eba968 +0 Aspose.Word.File.a6.a(Aspose.Word.File.b, Aspose.Word.File.y, System.IO.BinaryReader))

337fd0d8 07ea188c (MethodDesc 0x7eb0aa0 +0x19c Aspose.Word.File.a0..ctor(System.IO.BinaryReader, Int32, Int32)), calling (MethodDesc 0x7eb2a78 +0 Aspose.Word.File.ap.a(Aspose.Word.File.a0))

337fd0f8 07ea051c (MethodDesc 0x7b4ebd0 +0x18c Aspose.Word.RW.Doc.Reader.e.a(Aspose.Word.File.ai)), calling (MethodDesc 0x7eb0aa0 +0 Aspose.Word.File.a0..ctor(System.IO.BinaryReader, Int32, Int32))

337fd13c 79e7bbb1 mscorwks!PreStubWorker+0x138, calling mscorwks!_EH_epilog3

337fd140 00331efe 00331efe, calling mscorwks!PreStubWorker

337fd158 07ea0349 (MethodDesc 0x5c667b8 +0x71 Aspose.Word.Document.a(Aspose.Word.File.ai)), calling (MethodDesc 0x7b4ebd0 +0 Aspose.Word.RW.Doc.Reader.e.a(Aspose.Word.File.ai))

337fd178 07ea0349 (MethodDesc 0x5c667b8 +0x71 Aspose.Word.Document.a(Aspose.Word.File.ai)), calling (MethodDesc 0x7b4ebd0 +0 Aspose.Word.RW.Doc.Reader.e.a(Aspose.Word.File.ai))

337fd190 07b6f450 (MethodDesc 0x5c667c0 +0x70 Aspose.Word.Document.a(System.String)), calling (MethodDesc 0x5c667b8 +0 Aspose.Word.Document.a(Aspose.Word.File.ai))

337fd194 00331efe 00331efe, calling mscorwks!PreStubWorker

337fd1ac 07b6f356 (MethodDesc 0x5c66700 +0x6 Aspose.Word.Document..ctor(System.String)), calling (MethodDesc 0x5c667c0 +0 Aspose.Word.Document.a(System.String))

337fd1cc 07b6f356 (MethodDesc 0x5c66700 +0x6 Aspose.Word.Document..ctor(System.String)), calling (MethodDesc 0x5c667c0 +0 Aspose.Word.Document.a(System.String))

337fd1d0 07b6f0e6 (MethodDesc 0x5c63cd8 +0x7e Chatham.MergeManager.AsposeWord.AsposeWordMergeManager.CreateMergeDocuments(Chatham.MergeManager.MergeManagerTask)), calling (MethodDesc 0x5c66700 +0 Aspose.Word.Document..ctor(System.String))

337fd1ec 07b6efd4 (MethodDesc 0x5c63ce0 +0x34 Chatham.MergeManager.AsposeWord.AsposeWordMergeManager.MergeTask(Chatham.MergeManager.MergeManagerTask))

337fd1f8 07b6ee5e (MethodDesc 0x5c63cd0 +0x2e Chatham.MergeManager.AsposeWord.AsposeWordMergeManager.Merge(Chatham.MergeManager.MergeManagerTask, Aspose.Word.SaveFormat, System.IO.Stream))

337fd204 056dc8b0 (MethodDesc 0x33970a0 +0x950 Chatham.Reports.PaymentNotices.PaymentNoticesGenerator.Generate(Int32, System.DateTime)), calling (MethodDesc 0x5c63cd0 +0 Chatham.MergeManager.AsposeWord.AsposeWordMergeManager.Merge(Chatham.MergeManager.MergeManagerTask, Aspose.Word.SaveFormat, System.IO.Stream))

337fd5e8 034510a7 (MethodDesc 0x3395e58 +0x527 Chatham.Reports.PaymentNotices.PaymentNoticesBatchProcess.Start()), calling (MethodDesc 0x33970a0 +0 Chatham.Reports.PaymentNotices.PaymentNoticesGenerator.Generate(Int32, System.DateTime))

337fd608 034510a7 (MethodDesc 0x3395e58 +0x527 Chatham.Reports.PaymentNotices.PaymentNoticesBatchProcess.Start()), calling (MethodDesc 0x33970a0 +0 Chatham.Reports.PaymentNotices.PaymentNoticesGenerator.Generate(Int32, System.DateTime))

337fd618 79e7bba9 mscorwks!PreStubWorker+0x130, calling ntdll!RtlRestoreLastWin32Error

337fd61c 79e7bbb1 mscorwks!PreStubWorker+0x138, calling mscorwks!_EH_epilog3

337fd664 79e7bbb1 mscorwks!PreStubWorker+0x138, calling mscorwks!_EH_epilog3

337fd668 00331efe 00331efe, calling mscorwks!PreStubWorker

337fd680 0345019a (MethodDesc 0x3393548 +0x6a Chatham.PandA.Batch.ProcessManager.AppDomainLoader.Start()), calling 03406062

337fd6a0 0345019a (MethodDesc 0x3393548 +0x6a Chatham.PandA.Batch.ProcessManager.AppDomainLoader.Start()), calling 03406062

337fd6b0 79e88f63 mscorwks!CallDescrWorker+0x33

337fd6d0 79e88f63 mscorwks!CallDescrWorker+0x33

337fd6e0 79e88ee4 mscorwks!CallDescrWorkerWithHandler+0xa3, calling mscorwks!CallDescrWorker

337fd704 71ce4c91 kerberos!KerbFreeList+0x7b47

337fd740 71ce4c91 kerberos!KerbFreeList+0x7b47

337fd760 7a122fcf mscorwks!CallDescrWithObjectArray+0x3fa, calling mscorwks!CallDescrWorkerWithHandler

337fd7a4 79e908f2 mscorwks!MetaSig::SizeOfActualFixedArgStack+0x12, calling mscorwks!MetaSig::ForceSigWalk

337fd7a8 7a122d44 mscorwks!CallDescrWithObjectArray+0xa9, calling mscorwks!ClrSafeInt<unsigned int>::addition

337fd7b4 7a122d50 mscorwks!CallDescrWithObjectArray+0xb5, calling mscorwks!_alloca_probe_16

337fd83c 7a12342f mscorwks!CStackBuilderSink::PrivateProcessMessage+0x273, calling mscorwks!CallDescrWithObjectArray

337fd884 79e74411 mscorwks!ClrFlsSetValue+0x57, calling mscorwks!_EH_epilog3

337fd8ac 79e74411 mscorwks!ClrFlsSetValue+0x57, calling mscorwks!_EH_epilog3

337fd8b0 79e74de7 mscorwks!CantAllocThreads::UnmarkThread+0x49, calling mscorwks!ClrFlsSetValue

337fd8c8 79e74dad mscorwks!ExecutionManager::DecrementReader+0x10, calling mscorwks!DecrementMP

337fd8cc 79e74d93 mscorwks!Holder<ExecutionManager *,&ExecutionManager::IncrementReader,&ExecutionManager::DecrementReader,0,&NoNull<ExecutionManager *>,2>::~Holder<ExecutionManager *,&ExecutionManager::IncrementReader,&ExecutionManager::DecrementReader,0,&NoNull<ExecutionManager *>,2>+0x22, calling mscorwks!ExecutionManager::DecrementReader

337fd8d0 79e74d9c mscorwks!Holder<ExecutionManager *,&ExecutionManager::IncrementReader,&ExecutionManager::DecrementReader,0,&NoNull<ExecutionManager *>,2>::~Holder<ExecutionManager *,&ExecutionManager::IncrementReader,&ExecutionManager::DecrementReader,0,&NoNull<ExecutionManager *>,2>+0x2b, calling mscorwks!_EH_epilog3

337fd8f8 79e74c1c mscorwks!Alloc+0x60

337fd914 79e88774 mscorwks!AllocateArrayEx+0x1d1, calling mscorwks!Alloc

337fd940 79e81545 mscorwks!ClassLoader::LookupTypeHandleForTypeKeyInner+0x3a, calling mscorwks!ClassLoader::LookupInPreferredZapModule

337fd958 79e814f3 mscorwks!ClassLoader::LookupTypeHandleForTypeKey+0x12, calling mscorwks!ClassLoader::LookupTypeHandleForTypeKeyInner

337fd970 79e82b40 mscorwks!ClassLoader::LoadConstructedTypeThrowing+0x18, calling mscorwks!ClassLoader::LookupTypeHandleForTypeKey

337fd978 79e82b68 mscorwks!ClassLoader::LoadConstructedTypeThrowing+0x87, calling mscorwks!_EH_epilog3

337fd9a8 79e8168a mscorwks!ClassLoader::LoadArrayTypeThrowing+0x7e, calling mscorwks!ClassLoader::LoadConstructedTypeThrowing

337fd9e0 79f78b0a mscorwks!SignatureNative::GetSignature+0x25d, calling mscorwks!AllocateArrayEx

337fd9ec 79f78b5c mscorwks!SignatureNative::GetSignature+0x2ef, calling mscorwks!Frame::Pop

337fd9f0 79f78b67 mscorwks!SignatureNative::GetSignature+0x2fa, calling mscorwks!HelperMethodFrameRestoreState

337fda00 79f78b8a mscorwks!SignatureNative::GetSignature+0x31d, calling mscorwks!__security_check_cookie

337fda1c 79e771e9 mscorwks!Thread::StackWalkFrames+0xae, calling mscorwks!Thread::StackWalkFramesEx

337fda34 79f789a2 mscorwks!SignatureNative::GetSignature+0x67, calling mscorwks!LazyMachStateCaptureState

337fdab4 7a1231e8 mscorwks!CStackBuilderSink::PrivateProcessMessage+0x5a, calling mscorwks!LazyMachStateCaptureState

337fdaf4 79ef59c7 mscorwks!MetaDataImport::EnumCount+0xe0

337fdba0 79eea85e mscorwks!DispatchSlot::GetMethodDesc+0x11, calling mscorwks!MethodTable::GetUnknownMethodDescForSlotAddress

337fdbac 79eeaf5f mscorwks!VirtualCallStubManager::Resolver+0x10f, calling mscorwks!MethodDesc::IsGenericMethodDefinition

337fdbc4 79e8116f mscorwks!MethodTable::GetUnknownMethodDescForSlotAddress+0x4d, calling mscorwks!MethodDesc::GetMethodDescFromStubAddr

337fdbd0 79e7bf3e mscorwks!MethodDesc::IsRestored+0x2d, calling mscorwks!MethodTable::IsRestored

337fdbe8 794be820 (MethodDesc 0x7913eef0 +0x20 System.Runtime.Remoting.Messaging.StackBuilderSink.PrivateProcessMessage(System.RuntimeMethodHandle, System.Object[], System.Object, Int32, Boolean, System.Object[] ByRef)), calling mscorwks!CStackBuilderSink::PrivateProcessMessage

337fdc08 794bdf4b (MethodDesc 0x79248210 +0x38b System.Runtime.Remoting.Messaging.StackBuilderSink.SyncProcessMessage(System.Runtime.Remoting.Messaging.IMessage, Int32, Boolean)), calling (MethodDesc 0x7913eef0 +0 System.Runtime.Remoting.Messaging.StackBuilderSink.PrivateProcessMessage(System.RuntimeMethodHandle, System.Object[], System.Object, Int32, Boolean, System.Object[] ByRef))

337fdc74 79e8a1af mscorwks!HelperMethodFrame_1OBJ::HelperMethodFrame_1OBJ+0x14, calling mscorwks!HelperMethodFrame::HelperMethodFrame

337fdc94 794bdba9 (MethodDesc 0x79248208 +0x9 System.Runtime.Remoting.Messaging.StackBuilderSink.SyncProcessMessage(System.Runtime.Remoting.Messaging.IMessage))

337fdca0 794c0bf9 (MethodDesc 0x792481b8 +0xcd System.Runtime.Remoting.Messaging.ServerObjectTerminatorSink.SyncProcessMessage(System.Runtime.Remoting.Messaging.IMessage))

337fdcb4 794c0832 (MethodDesc 0x79274910 +0x15a System.Runtime.Remoting.Messaging.ServerContextTerminatorSink.SyncProcessMessage(System.Runtime.Remoting.Messaging.IMessage)), calling 006abf6a

337fdccc 794995a8 (MethodDesc 0x792433c8 +0x74 System.Runtime.Remoting.Contexts.Context.NotifyDynamicSinks(System.Runtime.Remoting.Messaging.IMessage, Boolean, Boolean, Boolean, Boolean))

337fdcf0 79499c0a (MethodDesc 0x79271298 +0xfa System.Runtime.Remoting.Channels.CrossContextChannel.SyncProcessMessageCallback(System.Object[])), calling 006a75ee

337fdd14 79e74d9c mscorwks!Holder<ExecutionManager *,&ExecutionManager::IncrementReader,&ExecutionManager::DecrementReader,0,&NoNull<ExecutionManager *>,2>::~Holder<ExecutionManager *,&ExecutionManager::IncrementReader,&ExecutionManager::DecrementReader,0,&NoNull<ExecutionManager *>,2>+0x2b, calling mscorwks!_EH_epilog3

337fdd18 79e816dd mscorwks!ExecutionManager::FindZapModule+0x4b, calling mscorwks!_EH_epilog3

337fdd30 793564dc (MethodDesc 0x7913beb0 +0x8 System.Threading.Thread.CompleteCrossContextCallback(System.Threading.InternalCrossContextDelegate, System.Object[]))

337fdd34 79e88f63 mscorwks!CallDescrWorker+0x33

337fdd44 79e88ee4 mscorwks!CallDescrWorkerWithHandler+0xa3, calling mscorwks!CallDescrWorker

it's Archive about 'IoCompletion handle...'

IoCompletion handle