64位环境下!heap -l的结果是不是有问题啊

多谢张老师和各位老师吗，我这里遇到个问题，一个64位的程序，内存一直在增长，我dump出来用windbg查看，!heap -l的结果有点奇怪，其中的Size部分是分配的堆块的大小吧？可是除了第一个堆栈是110之外，其他打印出来的Size都是0，这是为什么呢？

0:000> !heap -l 00000000026e0000

Searching the memory for potential unreachable busy blocks.

Heap 00000000024a0000

Heap 0000000000a10000

Heap 00000000026e0000

Heap 0000000002d00000

Heap 00000000147a0000

Heap 0000000015300000

Heap 00000000485e0000

Heap 0000000053ea0000

Heap 000000004bb90000

Heap 0000000053e90000

Heap 0000000054820000

Heap 0000000055bc0000

Heap 00000000582f0000

Scanning VM ...

Scanning references from 5577820 busy blocks (671 MBytes) ...........................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................

Entry             User              Heap              Segment               Size  PrevSize  Unused    Flags

-------------------------------------------------------------------------------------------------------------

00000000024a6cd0  00000000024a6d00  00000000024a0000  00000000024a0000       110        80        2c  busy  stack_trace

00007ff883e67c24: ntdll!RtlAllocateHeap+0x000000000007c604

00007ff883e13cbb: ntdll!RtlpInsertAssemblyStorageMapEntry+0x0000000000000097

00007ff883e1352a: ntdll!RtlpResolveAssemblyStorageMapEntry+0x0000000000000232

00007ff883e132af: ntdll!RtlGetAssemblyStorageRoot+0x00000000000000ff

00007ff883de48a0: ntdll!sxsisol_SearchActCtxForDllName+0x0000000000000200

00007ff883de44f4: ntdll!RtlDosApplyFileIsolationRedirection_Ustr+0x0000000000000224

00007ff883de71fd: ntdll!LdrpApplyFileNameRedirection+0x000000000000042d

00007ff883de6ba6: ntdll!LdrpFindOrMapDependency+0x0000000000000176

00007ff883de6002: ntdll!LdrpLocateModuleDependencies+0x000000000000015e

00007ff883e26659: ntdll!LdrpMapAndSnapModules+0x0000000000000091

00007ff883de125c: ntdll!LdrpPrepareModuleForExecution+0x00000000000000cc

00007ff883e841ad: ntdll!LdrpInitializeProcess+0x0000000000001905

00007ff883e634e8: ntdll!_LdrpInitialize+0x0000000000088e38

00007ff883dda65e: ntdll!LdrInitializeThunk+0x000000000000000e

.....................................

.....................................

.....................................

                ....................................

...................................