3
请注意以下几点:dumpheap VS琴弦 - 不同的计数报道字符串的条目和不同长度的
0:000> !dumpheap -min 0n100000 -mt 00007fff6c9c16b8 -live
Address MT Size
0000009757e51038 00007fff6c9c16b8 116590
0000009757e6d7c8 00007fff6c9c16b8 121392
0000009757e8b218 00007fff6c9c16b8 160838
0000009757eb2680 00007fff6c9c16b8 160826
0000009757ed9ae0 00007fff6c9c16b8 179332
0000009767e51038 00007fff6c9c16b8 121516
0000009767e6eb08 00007fff6c9c16b8 129002
0000009767e8e318 00007fff6c9c16b8 154506
0000009767eb3ec8 00007fff6c9c16b8 153568
0000009767ed96c8 00007fff6c9c16b8 212294
0000009767f223e0 00007fff6c9c16b8 211356
0000009767f55da0 00007fff6c9c16b8 157274
0000009767f7c420 00007fff6c9c16b8 156336
0000009767fa26f0 00007fff6c9c16b8 215062
0000009767fd6f28 00007fff6c9c16b8 214124
0000009777e71070 00007fff6c9c16b8 130594
Statistics:
MT Count TotalSize Class Name
00007fff6c9c16b8 16 2594610 System.String
Total 16 objects
0:000> !strings /n:100000
Address Gen Length Value
---------------------------------------
0000009767ed96c8 LOH 106134
SET DEADLOCK_PRIORITY HIGH
DECLARE @CommittedCommitStateId INT = (Select PR...
0000009767f223e0 LOH 105665
SET DEADLOCK_PRIORITY HIGH
DECLARE @CommittedCommitStateId INT = (Select PR...
0000009767fa26f0 LOH 107518
SET DEADLOCK_PRIORITY HIGH
DECLARE @CommittedCommitStateId INT = (Select PR...
0000009767fd6f28 LOH 107049
SET DEADLOCK_PRIORITY HIGH
DECLARE @CommittedCommitStateId INT = (Select PR...
---------------------------------------
4 matching strings
通知书的,!dumpheap
报告16名现场的字符串,而!strings
仅报告4.
它们的长度是不同的。
为什么?
哇。我没有想到。很好的结论。 –