[Mono-dev] Help with heap profilers

[Bassam Tabbara]

Any help with this would be appreciated? What tools are folks using to find leaks / fragmentation issues on mono?

From: mono-devel-list-bounces at lists.ximian.com [mailto:mono-devel-list-bounces at lists.ximian.com] On Behalf Of Bassam Tabbara
Sent: Thursday, October 21, 2010 11:20 PM
To: mono-devel-list at lists.ximian.com
Subject: [Mono-dev] Help with heap profilers

I suspect I'm seeing a low grade leak with ASP.NET, and I'm having a hard time getting any of the heap profilers to run correctly. Which is the recommended heap profiler? I assume it's the logging profiler. I run it with the following options:

--profile=logging:gc,as,output=/mnt/profile/frontend.$$.mprofile

And it seems to hang my process frequently both while running and during shutdown. Also even when it does not hang, I'm unable to get mprof-decoder to parse its output, I see the following exception quite frequently:

Unhandled Exception: System.OverflowException: Number overflow.
  at Mono.Profiler.BlockData.DecodeHeaderBlockCounterDelta (System.Byte[] header) [0x00000] in <filename unknown>:0
  at Mono.Profiler.SyncLogFileReader.ReadBlock () [0x00000] in <filename unknown>:0
  at Mono.Profiler.ConsoleDecoder.Main (System.String[] argv) [0x00000] in <filename unknown>:0

Any help would be appreciated. I'm using mono built from mono-2-6 branch.

Thanks!
Bassam
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ximian.com/pipermail/mono-devel-list/attachments/20101023/ff24bf3f/attachment.html