[Mono-devel-list] Memory management for long running processes (desc-heap profiler)

[Ben Maurer]

On Tue, 2005-03-29 at 20:31 +0100, Alex Chudnovsky wrote:
> Right, I had a good run with desc-heap profiler, and it appears to 
> generate the following output:
> 
> Checkpoint at 1123773 for gc
>    System.String : 1168888
>    System.Int32 : 379812
>    System.Int32[] : 3329420
>    System.Collections.Hashtable+Slot[] : 5852760
>    System.Byte[] : 5869466
> Checkpoint at 1141329 for gc
>    System.String : 1184578
>    System.Int32 : 375684
>    System.Int32[] : 3329360
>    System.Collections.Hashtable+Slot[] : 5852760
>    System.Byte[] : 5889538
> 
> etc
> 
> -------
> 
> Now, this is all nice, but actual memory used by the application is much 
> much more to the tune of 100Mb+
> - am I misreading something here? Where are the other objects? They 
> might take no memory, but what does then?!?!

It gives you an output of the largest stuff.

Where did you get the 100+ mb from?

Can you try running with GC_PRINT_STATS=yes mono foo.exe?

-- Ben