[Mono-dev] Need help tracking this bug...

[Joe Shaw]

Hi Alan,

On 3/29/07, Alan McGovern <alan.mcgovern at gmail.com> wrote:
> I ran it again, and came up with this (startling ;) ) figures for
> allocations:
>
> 1) type=System.Runtime.Remoti...ing.MonoMethodMessage 4185
> 1024.1M 256603.6   0.5
>      System.Threading.ThreadPool:QueueUserWorkItem
>
>                     System.Timers.Timer:StartTimer
>
>
> What the hell? 1 gig of allocations from a System.Timers.Timer? Whats going
> on here!?

Yep, that's your problem right there. ;)  Also, if you look at the
summary you posted, you'll notice that in the course of 1 second, you
have 9 resizes going from a size of 2.8 megs to 322.6 megs.

On the surface it looks like a Mono bug, or possibly a bug in the
amount of data you're processing through remoting.  As Miguel
suggested, using heap-shot at this point will be helpful in finding
out what objects are allocating these and hopefully why.

Joe