Microsoft KB Archive/75359

{|
 * width="100%"|

PRB: One Cause of Fatal Exit 0x0140 &quot;Local Heap Is Busy&quot;

 * }

Q75359

-

The information in this article applies to:


 * Microsoft Windows Software Development Kit (SDK) versions 3.0, 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 query words: 3.00 3.10

Keywords : kb16bitonly

Issue type :

Technology : kbAudDeveloper kbWin3xSearch kbSDKSearch kbWinSDKSearch kbWinSDK300 kbWinSDK310