locked
DebugDiag Memory Pressure analysis doubt RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    I am using DebugDiag 1.2 to perform memory analysis of a .NET application.

    On taking a dump, and analyzing non .NET memory (third option on Advanced Analysis tab of the tool), I see two sections -

    Virtual Memory Summary
Size of largest free VM block   6.24 TBytes 
Free memory fragmentation   21.92% 
Free Memory   7.99 TBytes   (99.93% of Total Memory) 
Reserved Memory   4.06 GBytes   (0.05% of Total Memory) 
Committed Memory   1.49 GBytes   (0.02% of Total Memory) 
Total Memory   8.00 TBytes 
Largest free block at   0x00000005`16fc6000

    and -

    Virtual Allocation Summary
Reserved memory   3.96 GBytes 
Committed memory   1.08 GBytes 
Mapped memory   13.87 MBytes 
Reserved block count   58 blocks 
Committed block count   102 blocks 
Mapped block count   37 blocks

    Which of these pertain to the process im monitoring ? The private bytes for my process reported at the time the dump was taken are 1.43 GB.

    Tuesday, September 3, 2013 5:59 AM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Cygnus712,

    Welcome to MSDN forums.

    According to your description, there is a trouble in using Debugdiag.

    In my opinion, the thread is more related to the Windows Desktop Debugging forum. To solve it ASAP, I would suggest you post it in the Windows Desktop Debugging forum where you can contact Windows Desktop Debugging experts.

    Windows Desktop Debugging forum:http://social.msdn.microsoft.com/Forums/windowsdesktop/en-US/home?forum=windbg

    Thanks for your understanding.

    Regards,

    Damon

    <THE CONTENT IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND, WHETHER EXPRESS OR IMPLIED>
    Thanks
    MSDN Community Support

    Please remember to "Mark as Answer" the responses that resolved your issue. It is a common way to recognize those who have helped you, and makes it easier for other visitors to find the resolution later.

    Wednesday, September 4, 2013 10:56 AM