16-Bit Process Creation Can Result in Memory Loss

Last reviewed: May 5, 1997
Article ID: Q126277

The information in this article applies to:

Microsoft Windows NT Workstation version 3.5
Microsoft Windows NT Server version 3.5

SYMPTOMS

If a 16-bit Windows-based application creates another 16-bit Windows-based applications, the WOW environment can lose memory. Continuous memory loss can cause applications to fail.

CAUSE

Thread objects are lost when on 16-bit processes creates another 16-bit processes. Also, the Win16 GetIconInfo() function causes memory loss when memory is not correctly de-allocated.

RESOLUTION

To correct this problem, obtain and install Windows NT U.S. Service Pack 2.

STATUS

Microsoft has confirmed this to be a problem in Windows NT Workstation and Windows NT Server version 3.5. This problem has been corrected in the latest U.S. Service Pack for Windows NT version 3.5. For information on obtaining the Service Pack, query on the following word in the Microsoft Knowledge Base (without the spaces):

   S E R V P A C K

This problem was corrected in Windows NT version 3.51.

Additional query words: prodnt loss windows on windows
Keywords : kbbug3.50 kbfix3.51 kbother nt16ap
Version : 3.5
Platform : WINDOWS

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