none
ANTS profiler results and fragmentation issue RRS feed

  • Question

  • I am using the ANTS memory profiler for analyzing the continuous increase in memory consumption of a .NET application. I am facing an issue in understanding one of the components of the profiler results.

    In the image of the summary tab of the results -

    It shows the largest fragment being 67.66 MB, unused memory by .NET 625.3 MB and size of objects on large object heap as 112 KB.

    When the large object heap is so small, how can there be fragmentation ? And shouldn't the size of the largest fragment be more or less same as the unused .NET space ? Or am I missing something ?





    Tuesday, September 3, 2013 4:27 AM

Answers

  • Hi Cygnus,

    You have raised three big question about Garbage collection mechanism. I somewhat doubt the memory profiler here. If you want to know the core of the garbage collection mechanism, I recommend you to read some articles about GC. What we can do is to show you the references.

    # Garbage Collection: Automatic Memory Management in the Microsoft. Net Framework

    http://msdn.microsoft.com/en-us/magazine/bb985010.aspx

    Also I suggest you to read a book “CLR via C#”, you could find it in http://www.amazon.com/

    Hope useful to you.

    Best Regards,


    <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 12:50 AM
    Moderator