BUG: GlobalCompact() May Return an Inaccurate Value

Last reviewed: January 5, 1995
Article ID: Q111603

The information in this article applies to:

Microsoft Windows Software Development Kit (SDK) for Windows version 3.1

SYMPTOMS

GlobalCompact() may return a very inaccurate value when paging is enabled.

CAUSE

This is the value that is returned by a DPMI call. It is simply the largest hole in the linear address space and is not necessarily the largest block that can be allocated.

RESOLUTION

Allocate only as much memory as needed, and always check the return value from a call to a memory allocation routine.

STATUS

Microsoft has confirmed this to be a bug in Windows version 3.1. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

Additional reference words: buglist3.10 3.10
KBCategory: kbprg kbbuglist
KBSubcategory: KrMm

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