本文介绍了DebugDiag在胜利10上打破的处理方法，对大家解决问题具有一定的参考价值，需要的朋友们下面随着小编来一起学习吧！
问题描述
我尝试使用DebugDiag 2.0 Update 1来分析本机应用程序内存转储。
（Win 10 ent x64 8Gb RAM，vs 2015 pro，wdk 10）
DebugDiag可以很好地分析来自不同机器（win 7）的任何转储文件，而不是我的。
但是如果我在我的机器上进行任何内存转储，DebugDiag显示奇怪结果。示例：
最大空闲VM块的大小 |
1,11 GBytes |
可用内存碎片 |
40,36％ |
可用内存 |
1,86 GBytes （总内存的0％） |
预留记忆 |
128 TBytes （总内存的100％）< --- ?????????¥b $ b |
承诺记忆 |
< span style ="color：saddlebrown"> 102,05 MBytes （总内存的0％） |
总内存 |
128 TBytes |
最大的免费区块 |
0x00000000`1001c000 |
虚拟内存详细信息
<表格边框="0">
论坛。
Karl
I try to use DebugDiag 2.0 Update 1 to analyze native app memory dumps.
(Win 10 ent x64 8Gb RAM, vs 2015 pro, wdk 10)
DebugDiag analyzes fine any dump file coming from different machine (win 7) than mine.
However if I take any memory dump on my machine, DebugDiag show strange result. Example:
| Size of largest free VM block |
1,11 GBytes |
| Free memory fragmentation |
40,36% |
| Free Memory |
1,86 GBytes (0% of Total Memory) |
| Reserved Memory |
128 TBytes (100% of Total Memory) <--- ?????????
|
| Committed Memory |
102,05 MBytes (0% of Total Memory) |
| Total Memory |
128 TBytes |
| Largest free block at |
0x00000000`1001c000 |
Virtual Memory Details
|
|
|
128 TBytes <-- ??????
|
| 73,52 MBytes |
| 3,93 MBytes |
| 4 KBytes |
| 0 Bytes |
| 9,44 MBytes |
|
Heap Summary
| Number of heaps |
2 Heaps |
| Total reserved memory |
7523136 TBytes <---- ?????
|
| Total committed memory |
14684736 TBytes <--- ?????
|
And so on, and the Heap details part ends with a System.OverflowException
| Heap Name |
Default process heap |
| Heap Description |
This heap is created by default and shared by all modules in the process |
| Reserved memory |
0 Bytes |
| Committed memory |
3473408 TBytes(?% of reserved) <--- ??????
|
| Uncommitted memory |
|
|
|
Analysis Rule Summary |
| |
| Rule Name |
Status |
Details |
| MemoryAnalysis |
Failed |
Dump File: removed by me;
Type: System.OverflowException
Message: Value was either too large or too small for an Int32.
Stack Trace:
System.Convert.ToInt32(Double value)
DebugDiag.AnalysisRules.HelperFunctionsImpl.PrintMemory(Double Memory)
DebugDiag.AnalysisRules.HeapFunctionsImpl.PrintHeapInfo(INTHeap Heap)
DebugDiag.AnalysisRules.HeapFunctionsImpl.AnalyzeAndReportHeapInfo()
DebugDiag.AnalysisRules.MemoryAnalysis.RunAnalysisRule(NetScriptManager manager, NetProgress progress)
DebugDiag.DotNet.NetAnalyzer.RunAnalysisRulesInternal(DumpFileType bitness, NetProgress progress, String symbolPath, String imagePath, String reportFileFullPath, Boolean twoTabs, AnalysisModes analysisMode) |
|
|
解决方案 Hello,
The Windows Desktop Perfmon and Diagnostic tools forum is to discuss performance monitor (perfmon), resource monitor (resmon), and task manager, focusing on HOW-TO, Errors/Problems, and usage scenarios.
As the question is off topic here, I am moving it to the
Where is the Forum... forum.
Karl
这篇关于DebugDiag在胜利10上打破的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
查看全文
| |
