Possible Causes for System Resource Reduction

 Last reviewed: July 7, 1997
Article ID: Q66654
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

You can note via Program Manager's "About Box" that Windows's System Resources can be inadvertently reduced by a Windows-based application, causing subsequent RegisterWindow() or CreateWindow() function calls to fail.

The system resources are a reflection of the lower USER and GDI's data segments. The following steps eliminate the major causes of USER's data segment fill-up listed in each step:

  1. Ensure that the cbClsExtraBytes and cbWndExtraBytes are set to 0 in the WNDCLASS structure, unless the application is definitely using them.

  2. Ensure that a MakeProcInstance() is performed and the window procedure is EXPORTed in the .DEF file.

  3. Use CVW to verify that the application is receiving the WM_CREATE message.

  4. Confirm that all menus created, loaded, or added dynamically [that is, using CreateMenu(), AppendMenu(), and so forth] are properly destroyed before terminating the application.

The main reason why GDI's data segment fills up is that objects are being created and are not being destroyed when they are no longer needed.

Additional reference words: 3.00 3.10
KBCategory: kbprg
KBSubcategory: UsrSys

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