Article ID: 981651 - View products that this article applies to.
The Microsoft Visual Studio 2008 Service Pack 1 (SP1) IDE crashes when you try to open a large Microsoft Team Foundation Server (TFS) build report in the build explorer.
This problem occurs because the TFS control that processes the WM_PAINT message tries to create a bitmap file by calling the CreateDIBSection function. This bitmap file is hundreds of megabytes (MB). However, the operating system has insufficient contiguous virtual address space to create this bitmap file. In this situation, the CreateDIBSection function fails and throws an exception.
Hotfix informationA 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 software update 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:
PrerequisitesYou must have Microsoft Visual Studio 2008 Team Foundation Server SP1 installed to apply this hotfix.
Restart requirementYou do not have to restart the computer after you apply the hotfix.
Hotfix replacement informationThis hotfix does not replace any other hotfixes.
File informationThe English 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.
Collapse this tableExpand this table
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.