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

[Marcos Cobeña Morián]

Hi Alan,

If you can run your application on Windows, check this tool which can
help to find where's located memory leak:
http://www.microsoft.com/downloads/details.aspx?amp;amp;displaylang=en&familyid=9bfa49bc-376b-4a54-95aa-73c9156706e7&displaylang=en.

This guide can also help:
http://support.microsoft.com/?scid=kb%3Ben-us%3B919790&x=11&y=15.

>From your e-mail, it seems to be those AsyncSockets not disposing as expected.

Cheers,

2007/3/30, Alan McGovern <alan.mcgovern at gmail.com>:
> Hi,
>
> > 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.
>
> Yup, i had noticed that ;) There is something fishy, but i can't find out
> what it is. I've run heap-shot and attached and emailed the results in
> already. Hopefully they'll make sense to someone. By the looks of it,
> there's some kind of problem internal to mono which is resulting in this
> rapid memory usage as on MS.NET this doesn't happen. There could easily be a
> bug in my own code and MS.NET just handles it better, but i have no idea
> what is causing the problem to start off with, so i can't fix it.
>
> Im not using remoting as such, I assume that internally AsyncSockets make
> use of the remoting framework. I do make heavy use of those, but i'm using
> them in the way they're supposed to be used.
>
> Any further advice would be brilliant.
>
> Alan.
>
> _______________________________________________
> Mono-devel-list mailing list
> Mono-devel-list at lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/mono-devel-list
>
>


-- 
Marcos - http://www.youcannoteatbits.org