FIX: You receive an access violation in std::ios_base under low memory conditions

This article has been archived. It is offered "as is" and will no longer be updated.
Under low memory conditions, Microsoft Visual C++ .NET applications may receive an access violation and crash suddenly. The stack trace of the crash will be the following:
01 MODULE!std::ios_base::_Callfns+0x902 MODULE!std::ios_base::_Tidy+0xb03 MODULE!std::ios_base::~ios_base+0x29
This problem occurs because the required initialization in the C++ Runtime Library does not occur because of memory allocation failures.
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it 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 Microsoft Visual Studio .NET 2003 service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product 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.

The English version of this hotfix has the file attributes (or later) 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 tool in Control Panel.
   Date         Time      Version      Size       File name   ----------------------------------------------------------------------------   06-Feb-2004  11:29:38                   4,246  Ios.cpp   24-Feb-2004  22:42:14               3,604,312  Libcp.lib   24-Feb-2004  22:42:13                 217,088  Libcp.pdb   24-Feb-2004  22:47:45               4,433,756  Libcpd.lib   24-Feb-2004  22:47:44                 225,280  Libcpd.pdb   24-Feb-2004  22:44:22               3,654,604  Libcpmt.lib   24-Feb-2004  22:44:22                 217,088  Libcpmt.pdb   24-Feb-2004  22:49:49               4,449,870  Libcpmtd.lib   24-Feb-2004  22:49:48                 233,472  Libcpmtd.pdb   24-Feb-2004  23:33:33  7.10.4055.0    499,712  Msvcp71.dll   24-Feb-2004  23:33:33               2,976,768  Msvcp71.pdb   24-Feb-2004  22:51:13  7.10.4055.0    765,952  Msvcp71d.dll   24-Feb-2004  22:51:13               2,624,512  Msvcp71d.pdb   25-Feb-2004  19:33:34                 151,040  VC_User_STL71_RTL_X86_---.msm
One way to obtain the call stack that is listed in the "Symptoms" section of this article is to use ADPlus. Use the ADPlus tool to obtain memory dumps of crashed processes. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
286350 HOW TO: Use ADPlus to troubleshoot "hangs" and "crashes"
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section of this article.

Article ID: 837421 - Last Review: 01/17/2015 07:07:43 - Revision: 2.2

Microsoft Visual Studio .NET 2003 Academic Edition, Microsoft Visual Studio .NET 2003 Enterprise Architect, Microsoft Visual Studio .NET 2003 Enterprise Developer, Microsoft Visual Studio .NET 2003 Professional Edition, Microsoft Visual C++ .NET 2003 Standard Edition

  • kbnosurvey kbarchive kbqfe kbhotfixserver kbvsnet2003sp1fix kbfix kbbug KB837421
ERROR: at System.Diagnostics.Process.Kill() at Microsoft.Support.SEOInfrastructureService.PhantomJS.PhantomJSRunner.WaitForExit(Process process, Int32 waitTime, StringBuilder dataBuilder, Boolean isTotalProcessTimeout)