INFO: Increased Stack Usage by Windows 2000 ComponentsID: Q232706
|
Some Windows 2000 components use more stack than they do in previous versions of Windows. If your application creates a very small stack, it may not work properly on Windows 2000.
In Windows 2000, several components, including ADVAPI32, OLE32, and SHELL32, use much more stack than they do in Windows NT 4.0 and previous versions. Performance enhancements and new features in Windows 2000 are responsible for the increase in stack consumption.
Although the amount of stack your application's components use may not change, most applications rely on some Windows components for functionality and integration with other applications and the operating system.
All stacks have a reserved size and a committed size. The reserved size is the size of the stack that is initially allocated for a thread. The committed size is the amount of memory the stack is currently using. Unless you need to free up address space or reduce memory use for performance reasons, you should use the default reserved stack size. If you designate a smaller size, you should thoroughly test your application with all of the components it can call including DLLs, OCXs, and COM controls. As a general rule, you should not set the reserved stack size to less than 100K.
For more information about processes and threads, see the DLLs, Processes, and Threads section of the Base Services documentation in the Platform SDK. You can view this documentation online at:
http://msdn.microsoft.com/library/sdkdoc/winbase/prothred_86sz.htm
Additional query words: compatguidechange
Keywords : kbWinOS2000 kbSDKWin32 kbDSupport
Version : WINDOWS:
Platform : WINDOWS
Issue type : kbinfo
Last Reviewed: July 2, 1999