Microsoft KB Archive/258965

= ImgEdit.ocx causes breakpoint in RtlFreeHeap when it is executed from Visual C++ Debugger =

Article ID: 258965

Article Last Modified on 1/10/2006

-

APPLIES TO


 * Microsoft Visual C++ 5.0 Enterprise Edition
 * Microsoft Visual C++ 6.0 Enterprise Edition
 * Microsoft Visual C++ 5.0 Professional Edition
 * Microsoft Visual C++ 6.0 Professional Edition
 * Microsoft Visual C++ 6.0 Standard Edition
 * Microsoft Visual C++ 2005 Express Edition
 * Microsoft Visual C++ .NET 2003 Standard Edition
 * Microsoft Visual C++ .NET 2002 Standard Edition
 * Microsoft Windows NT Server 4.0 Standard Edition
 * Microsoft Windows NT Workstation 4.0 Developer Edition

-



This article was previously published under Q258965



Note Microsoft Visual C++ .NET 2002 and Microsoft Visual C++ .NET 2003 support both the managed code model that is provided by the Microsoft .NET Framework and the unmanaged native Microsoft Windows code model. The information in this article applies only to unmanaged Visual C++ code. Microsoft Visual C++ 2005 supports both the managed code model that is provided by the Microsoft .NET Framework and the unmanaged native Microsoft Windows code model.



SYMPTOMS
When you use the ImgEdit.ocx control in a MFC application running on Windows NT 4.0, you may get a debug assertion in the RtlFreeHeap function when you exit a debug build of the application. However, when you employ the same control in Visual Basic, you do not encounter the debug assertion in RtlFreeHeap upon exiting. In addition, when you use the ImgEdit.ocx control in a release build of a MFC application on Windows NT 4.0, the control does not reveal this assertion. And the assertion does not appear when you you run the application on Windows 95, Windows 98 or Windows 2000, but appears on Windows NT 4.0.



CAUSE
This is a bug in the ImgEdit.ocx control. The assertion can be safely ignored because it is only given one time and that is when the application is shutting down. This assertion does not cause any problems when you are running in release builds.



RESOLUTION
Ignore the assertion as it is harmless in this case.



STATUS
This behavior is a bug in the ImgEdit.ocx control.

The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, regarding the performance or reliability of these products.

Additional query words: Wang Image Edit Control

Keywords: kbtshoot kbnofix kbinprocsvr kbprb kbctrl KB258965

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.