PRB: One Cause of Fatal Exit 0x0140 "Local Heap Is Busy"

Last reviewed: July 23, 1997
Article ID: Q75359

3.00 3.10 WINDOWS kbprg kbprb

The information in this article applies to:

Microsoft Windows Software Development Kit (SDK) for Windows versions 3.0 and 3.1

SYMPTOMS

The debugging version of Windows reports Fatal Exit 0x0140.

CAUSE

A module with no heap (such as a no-data dynamic-link library) uses LocalAlloc to allocate local memory. Even if the application does not call LocalAlloc directly, application startup code in the C run-time libraries allocates memory to store the command-line arguments.

RESOLUTION

Make sure that the proper library is specified on the LINK command line.

Additional reference words: 3.00 3.10
KBCategory: kbprg kbprb
KBSubcategory: KrDebug
Keywords : kb16bitonly

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 23, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.