ID Number: Q68654
3.00
WINDOWS
Summary:
SYMPTOMS
When attempting to walk the global heap, HEAPWALK displays the
message "Walking didn't work."
CAUSE
HEAPWALK is unable to allocate memory to store information about
the global heap.
RESOLUTION
Take steps to reduce the number of items that are allocated from
global memory, which might include closing one or more
applications. Then issue the request to walk the global heap again.
More Information:
When the user asks to walk the global heap, HEAPWALK builds a table
with about 50 bytes of information for each item in the global heap.
HEAPWALK uses LocalAlloc() to allocate memory for the table from its
own local heap. If there are many items in the global heap, as there
might be if many applications are running simultaneously, or if an
application has allocated many blocks of global memory, then the
LocalAlloc() may fail, and HEAPWALK displays the "Walking didn't work"
message.