Increasing the Desktop Application HeapID: Q126962
|
When you run a large number of Windows-based programs, "Out Of Memory" error messages appear when you attempt to start new programs or try to use programs that are already running, even though you still have plenty of physical and pagefile memory available.
This behavior can occur if the desktop heap in the WIN32 subsystem is
depleted.
NOTE
WARNING: Using Registry Editor incorrectly can cause serious problems that
may require you to reinstall your operating system. Microsoft cannot
guarantee that problems resulting from the incorrect use of Registry Editor
can be solved. Use Registry Editor at your own risk.
For information about how to edit the registry, view the "Changing Keys And
Values" Help topic in Registry Editor (Regedit.exe) or the "Add and Delete
Information in the Registry" and "Edit Registry Data" Help topics in
Regedt32.exe. Note that you should back up the registry before you edit it.
If you are running Windows NT, you should also update your Emergency
Repair Disk (ERD).
To correct this problem, increase the size of the desktop heap:
SharedSection=xxxx,yyyywhere xxxx defines the maximum size of the system-wide heap (in kilobytes) and yyyy defines the size of the per desktop heap. The default value of the per desktop heap under Windows NT 3.5 (512K) can support approximately 2,500 windows. Increasing the desktop heap by 256K or 512K normally provides enough memory to correct "Out of Memory" errors messages.
Windows NT uses a special memory heap for all Windows-based programs
running on the desktop. The desktop heap is used for all objects (windows,
menus, pens, icons, etc.). When a large number of Windows-based
programs are running, this heap may run out of memory. When there is
not enough memory to satisfy an allocation request, the system normally
returns an error and notifies the user that they are running low on
memory. Some programs do not handle the failure gracefully, and in some
cases there may not be enough memory to create the error message dialog box.
As a result, the requested operation fails without any indication.
The SharedSection key is a long string when viewed using Registry Editor.
The default value for this key is:
%SystemRoot%\system32\csrss.exe
ObjectDirectory=\Windows
SharedSection=1024,3072
Windows=On
SubSystemType=Windows
ServerDll=basesrv,1
ServerDll=winsrv:GdiServerDllInitialization,4
ServerDll=winsrv:UserServerDllInitialization,3
ServerDll=winsrv:ConServerDllInitialization,2
ProfileControl=Off
MaxRequestThreads=16
Additional query words: prodnt low failure fixed size page file
Keywords : kbenv ntconfig
Version : winnt:3.5,3.51,4.0
Platform : winnt
Issue type :
Last Reviewed: February 26, 1999