When you debug in Visual Studio 2008 Service Pack 1, more breakpoints are generated unexpectedly, or the IDE crashes or becomes unresponsive for about 15 seconds

When you debug in Microsoft Visual Studio 2008 Service Pack 1 (SP1), you experience one of the following symptoms.

Symptom 1

Consider the following scenario:
  • You build a project by using Microsoft intermediate language (MSIL) line code.
  • You use the IDE to open the executable file, and then you set a breakpoint to a method in a source line.
  • You start to debug.
In this scenario, more breakpoints to the same method are generated unexpectedly in other files.

Symptom 2

Consider the following scenario:
  • You open a Microsoft ASP.NET Web site, and then you set the Default.asp file as the home page.
  • You open the script file, and then you set a breakpoint in a line.
  • You run the ASP.NET Web site in the debug mode, and then you attach the debugger to the Dllhost.exe process.
  • You hit the breakpoint and continue to debug. Then, another page is displayed.
  • You stop debugging.
In this scenario, the IDE crashes. Additionally, the call stack may have information that resembles the following:
oleaut32.dll!APP_DATA::FreeCachedMem(void * pvData=0x0b031378, unsigned long cbData=144) Line 666 C++
oleaut32.dll!SysFreeString(wchar_t * bstr=0x0b03137c) Line 326 + 0xb bytes C++
> VSDebug.dll!CDebugDocument::~CDebugDocument() Line 469 C++
VSDebug.dll!CDebugDocument::`scalar deleting destructor'() + 0xd bytes C++ VSDebug.dll!CDebugDocument::Release() Line 485 C++
VSDebug.dll!CDebugDocumentManager::OnDocumentUnload(IDebugProperty2 * pProperty=0x0b03140c) Line 183 C++
VSDebug.dll!CDebugger::HandleEvent(IDebugEvent2 * pEvent=0x0b03140c, const _GUID & riidEvent={...}, bool IsStoppingEvent=false, IDebugProcess2 * pProcess=0x0affd4d0, IDebugProgram2 * pProgram=0x0af3ddb0, IDebugThread2 * pThread=0x00000000, bool fHandlingStoredEvent=false) Line 433 C++
VSDebug.dll!CDebugger::Event(IDebugEngine2 * pEngine=0x00000000, IDebugProcess2 * pProcess=0x0affd4d0, IDebugProgram2 * pProgram=0x0af3ddb0, IDebugThread2 * pThread=0x00000000, IDebugEvent2 * pEvent=0x0af9510c, const _GUID & riidEvent={...}, unsigned long dwAttrib=0) Line 123 C++
VSDebug.dll!sdm::CDebugManager::HandleEvent(tagSDM_EVENT_INFO eventInfo={...}, const _GUID & riidCallbackProxy={...}, void * pvProxy=0x0af7ffec) Line 75 C++
Note This problem does not occur again when you restart the Internet Information Services (IIS) server.

Symptom 3

When you set a breakpoint, the IDE becomes unresponsive for about 15 seconds.

Cause of symptom 1

This problem occurs because of an issue in the breakpoint binding logic.

Hotfix information

A supported hotfix is now available from Microsoft. However, it is intended to correct only the problem that is described in this article. Apply it only to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Visual Studio 2008 service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Customer Support Services to obtain the hotfix. For a complete list of Microsoft Customer Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.


You must have Visual Studio 2008 Service Pack 1 (SP1) installed to apply this hotfix.

Restart requirement

You do not have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

The global version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
File nameFile versionFile sizeDateTimePlatform
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates

Article ID: 967631 - Last Review: 10/07/2011 22:50:00 - Revision: 2.0

  • Microsoft Visual Studio 2008 Service Pack 1
  • kbsurveynew kbqfe kbfix KB967631