Visual Studio .NET may stop responding if the BoundsChecker tool is integrated with Visual Studio .NET or Visual Studio 2005 when you build a solution that contains multiple projects (843413)

SYMPTOMS

When you try to build a solution that contains multiple Microsoft Visual C++ .NET or Visual Studio 2005 projects, Microsoft Visual Studio .NET or Visual Studio 2005 may stop responding. You may notice this problem when you integrate the BoundsChecker tool with Visual Studio .NET.

Note The BoundsChecker tool is a third-party run-time error detection and debugging tool for Visual C++ .NET or Visual C++ 2005 developers.

CAUSE

The BoundsChecker tool calls the CConfigurationAssignmentExt::get_Extender method at the beginning of each project build. The get_Extender method creates an object of the CComBSTR class and an object of the CComVariant class. The CComBSTR object and the CComVariant object are assigned the same BSTR value. When these objects go out-of-scope, memory is freed two times. If the Visual Studio .NET or Visual Studio 2005 solution contains multiple projects, building the solution corrupts more memory and causes Visual Studio .NET or Visual Studio 2005 to stop responding.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

MORE INFORMATION

Memory is freed two times in both the CConfigurationAssignmentExt::get_Extender method and the CConfigurationAssignmentExt::get_ExtenderNames method. The CComBSTR object and the CComVariant object are assigned the same BSTR value in both the get_ExtenderNames method and the get_Extender method. Memory is freed two times when these objects go out-of-scope. Therefore, the repetitive calls to both these methods cause Visual Studio .NET or Visual Studio 2005 to stop responding.

REFERENCES

For more information, visit the following Component Source Web site:

http://www.componentsource.com/

Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.

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.