Heap and Stack Usage Within Windows

Last reviewed: July 22, 1997
Article ID: Q10641
3.00 3.10 WINDOWS kbprg

The information in this article applies to:

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

SUMMARY

The following information clarifies heap and stack usage within a segment versus heap and stack usage within the application as a whole, for Windows versions 3.0 and 3.1.

MORE INFORMATION

An application gets a single default data segment, from which the stack is allocated. The remainder of the data segment is used for static data and the dynamic local heap.

The STACKSIZE keyword in the .DEF file specifies the size of the application's stack; it is allocated from DGROUP and therefore is limited to a maximum size of (64K - heap size - static data) bytes. The stack size is not dynamically enlarged or reduced.

The HEAPSIZE keyword in the .DEF file specifies the initial default local heap size. Windows attempts to enlarge the heap size when local allocations fail; however, the heap is limited to a maximum size of (64K - stack size - static data).

The sum of the static data, stack, and local heap cannot exceed 64K.

Multiple local heaps can be managed using the LocalInit() call and swapping the DS register as needed. For more information on this technique, query on the following words:

   handle and limit and globalalloc and register

Chapter 18 (pages 707-724) of "Windows 3.0 Power Programming Techniques," by Paul Yao and Peter Norton (Bantam Computer Books), contains more details about this technique.


Additional reference words: 3.00 3.10
KBCategory: kbprg
KBSubcategory: KrTsksIns
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 22, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.