PRB: "Could not Load Debugee, Windows is Out of memory (1)"

 Last reviewed: July 22, 1997
Article ID: Q113969
1.50 WINDOWS kbinterop kbfile kbprb

The information in this article applies to:

  • The Visual Workbench Integrated Debugger included with: Microsoft Visual C++ for Windows, version 1.5

SYMPTOMS

The integrated debugger in Visual C++ 1.50 uses a DLL (TLW0NCL.DLL) that is unecessarily allocated in low memory (below one meg) and fixed there. This uses a valuable system resource that should be available for other applications.

The most common behavior is the appearance of a message box containing this error message: 

   Could not load debugee. Windows is Out of Memory (1)
This occurs when trying to run an application in the Visual Workbench debugger. One reason this can occur is because all of the memory below one megabyte is full. Typically, this will happen when many drivers are loaded, such as network or SCSI drivers.

RESOLUTION

Microsoft has released a patch to Visual C++ 1.5 which will allow the DLL for the debugger to load where Windows has room. This patch will modify the Visual Workbench 1.50, the new one will be version 1.50.01. VC1501.EXE can be downloaded as a self-extracting file from the Microsoft Software Library (MSL) on the following services:

  • Microsoft Download Service (MSDL) 

          Dial (206) 936-6735 to connect to MSDL
      Download VC1501.EXE. (size: 81078 bytes)
  • Internet (anonymous FTP) 

          ftp ftp.microsoft.com
      Change to the \softlib\mslfiles directory
      Get VC1501.EXE (size: 81078 bytes) 
      It can also be found in \developer\devtools\lang\msvcwin\public.
  • If you don't have access to the above services you may contact Microsoft Developer Support following the procedures outlined in the Obtaining Technical Support option on the Help menu of the Visual Workbench.

In addition, this patch will fix another problem with Visual C++ 1.50. The problem occurs when long strings are passed to OutputDebugString(), or when OutputDebugString() is called successively with no new-line characters. This may cause a general protection (GP) fault or cause the computer to hang (stop responding). For more information on this problem, query in the Microsoft Knowledge Base using these keywords: 

   OutputDebugString and Workbench and patch
This patch should only be applied when one of these problems is specifically encountered. These are the only two changes to Visual C++, version 1.5.

Additional reference words: 1.50 GPF
KBCategory: kbinterop kbfile kbprb
KBSubcategory WBDebug
Keywords : kb16bitonly kbfile kbinterop kbprb
Version : 1.50
Platform : WINDOWS

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: July 22, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.