Article ID: 331009
Article Last Modified on 5/29/2003
APPLIES TO
- Microsoft COM+ 1.0
- Microsoft Windows 2000 Service Pack 3
This article was previously published under Q331009
SYMPTOMS
Microsoft COM+ leaks memory during transactions with queued components. The leak includes two basic block sizes of 168 bytes and 206 bytes individually. The CoTaskMemAlloc API leaks. In both of the stacks that leak, you find COMSVCS!CNonRootTransactionStream::Create near the top of stack.
RESOLUTION
Service Pack Information
To resolve this problem, obtain the latest service pack for Microsoft Windows 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
260910 How to Obtain the Latest Windows 2000 Service Pack
Hotfix Information
To resolve this problem, obtain Microsoft COM+ Rollup Hotfix 24. For additional information, click the article number below to view the article in the Microsoft Knowledge Base:
810578 INFO: Availability of Windows 2000 Post-Service Pack 3 COM+ Hotfix Rollup Package 24
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Microsoft Windows 2000 Service Pack 4.
MORE INFORMATION
The memory leaks occur in the following stacks:
00b0f610 787be6f3
00b0f658 000bd248 00074fc8 COMSVCS!CNonRootTransactionStream::Create+0x8c
00b0f644 787df5c3 00b0f658 787df5d0 000bd248
COMSVCS!CSafeGuidToInterfaceMap::LookupOrCreate+0x83 00b0f664 787d84a2 000bd248
000bf224 787d7ea0 COMSVCS!CNonRootTransactionStream::FindOrCreate+0x23 00b0f670
787d7ea0 000bd248 787aaf42 000bf224
COMSVCS!CTransactionRepresentative::NeedEnvoy+0x12 00b0f678 787aaf42 000bf224
000bf224 00074fc8 COMSVCS!CNonRootTransaction::NeedEnvoy+0x20 00b0f6a4 787aa7ce
00074fc8 00074f20 00b0f780
COMSVCS!CStdContextActivator::AddTransactionProperty+0x192 00b0f730 787aa53a
00000003 00074f20 00b0f780 COMSVCS!CStdContextActivator::AddProperties+0x186
00b0f780 77a7e4ea 0009de78 00000000 000aad98
COMSVCS!CStdContextActivator::CreateInstance+0x19a 00b0f79c 77ad3c27 000aad98
00000000 000bd008 ole32!ActivationPropertiesIn::DelegateCreateInstance+0x4a
00b0f7c4 77d339c0 00078290 00000000 000aad98
ole32!CSurrogateProcessActivator::CreateInstance+0x9e 00b0f7e8 77d93570
77ad3b88 00b0f7fc 00000004 RPCRT4!Invoke+0x30 00b0fa54 77d949ac 000871d8
00081e38 0008ba48 RPCRT4!NdrStubCall2+0x63d 00b0fab8 77b29e7f 000871d8 0008ba48
00081e38 RPCRT4!CStdStubBuffer_Invoke+0xec 00b0fafc 77b29d6e 0008ba48 000870f4
00000000 ole32!SyncStubInvoke+0x61 00b0fb44 77aa7ae7 0008ba48 00087008 000871d8
ole32!StubInvoke+0xa8 00b0fba8 77aa7a33 00081e38 00000000 000871d8
ole32!CCtxComChnl::ContextInvoke+0xbb 00b0fbc4 77b29c89 0008ba48 00000001
000871d8 ole32!MTAInvoke+0x18 00b0fbf4 77b29a89 0008ba00 00081e38 000871d8
ole32!AppInvoke+0xb5 00b0fcb4 77b2a12c 000a58b0 00000000 000870d8
ole32!ComInvokeWithLockAndIPID+0x29e 00b0fcf4 77d33721 0008ba00 000870d8
0009a438 ole32!ThreadInvoke+0x1b7 00b0fd2c 77d33667 77b29f7b 0009a438 00b0fe0c
RPCRT4!DispatchToStubInC+0x84 00b0fd84 77d33579 00000000 00000000 00b0fe0c
RPCRT4!RPC_INTERFACE::DispatchToStubWorker+0x100 00b0fda4 77d48e81 0009a438
00000000 00b0fe0c RPCRT4!RPC_INTERFACE::DispatchToStub+0x5e 00b0fdd4 77d34bc6
0009a438 0009a3fc 00000000 RPCRT4!RPC_INTERFACE::DispatchToStubWithObject+0xa9
00b0fe10 77d346c5 000a1a48 000814a0 80020000
RPCRT4!LRPC_SCALL::DealWithRequestMessage+0x1c6 00b0fe28 77d422ff 0009a340
00b0fe50 000a1a48 RPCRT4!LRPC_ADDRESS::DealWithLRPCRequest+0x10c 00b0ff74
77d420d9 77d42528 000814a0 00070000
RPCRT4!LRPC_ADDRESS::ReceiveLotsaCalls+0x1eb 00b0ff78 77d42528 000814a0
00070000 0006f740 RPCRT4!RecvLotsaCallsWrapper+0x9 00b0ffa8 77d424da 00081428
00b0ffec 77e887dd RPCRT4!BaseCachedThreadRoutine+0x4f 00b0ffb4 77e887dd
0007ded0 00070000 0006f740 RPCRT4!ThreadStartRoutine+0x18 00b0ffec 00000000
77d424c2 0007ded0 00000000 KERNEL32!BaseThreadStart+0x52
Additional query words: kbWin2000preSP4COMRollup24Fix kbIISCOM
Keywords: kbbug kbpending kbwin2ksp4fix KB331009
