FIX: Memory Leak and Assertion Failure When You Call Through an Interceptor with a Large Call Stack (290516)


The information in this article applies to:

  • Microsoft COM+ 1.0
This article was previously published under Q290516

SYMPTOMS

You may encounter memory leaks in free (retail) builds or assertion failures in checked builds when you call the ICallFrame::Unmarshal or ICallFrame::Copy method to unmarshal or copy a call frame. The assertion failure may appear similar to the following error message:
Assertion failed: z:\src\nt\com\com1x\src\txf\callframe\callframe.h:521 m_pvArgs && WeOwn(m_pvArgs)

RESOLUTION

To resolve this problem, obtain the latest service pack for 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


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 Windows 2000 Service Pack 2.
Modification Type:MajorLast Reviewed:5/8/2002
Keywords:kbbug kbDSupport kberrmsg kbWin2000PreSP2Fix kbWin2000SP2Fix KB290516
©2002 Microsoft Corporation. All rights reserved.