PRB: GetFreeSpace Returns Physical Memory Not Free Heap Space

ID: Q137290

The information in this article applies to:

Microsoft Windows Software Development Kit (SDK) 3.1

SYMPTOMS

The GetFreeSpace API no longer returns the amount of free space on the global system heap.

CAUSE

Because Windows 95 implements virtual memory, the system heap is effectively unlimited. Returning the practical amount of free memory would cause unpleasant side effects in applications that assume the return value is limited to physical memory. Therefore, GetFreeSpace returns the amount of free space on the heap -- up to the amount of physical memory in the computer.

RESOLUTION

Do not depend on GetFreeSpace returning the amount of free space in the heap. It will not.

STATUS

This behavior is by design.

MORE INFORMATION

In particular, GetFreeSpace does not work with code that loops as shown in this pseudo code:


   while (there is still free memory)
      give it to me;

This programming practice is not supported. Applications must share system resources with each other. Applications can minimally use GetFreeSpace to determine a reasonable amount of memory to allocate for the current computer given their working set requirements.

NOTE: Win32-based applications should use GlobalMemoryStatus.

Additional query words: 4.00

Keywords : kbKernBase kbMemory kbDSupport kbGrpKernBase
Version : WINDOWS:3.1
Platform : WINDOWS
Issue type : kbprb