[Mono-dev] Need help tracking this bug...
Marcos Cobeña Morián
marcoscobena at gmail.com
Fri Mar 30 12:12:30 EDT 2007
If you can run your application on Windows, check this tool which can
help to find where's located memory leak:
This guide can also help:
>From your e-mail, it seems to be those AsyncSockets not disposing as expected.
2007/3/30, Alan McGovern <alan.mcgovern at gmail.com>:
> > 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.
> Mono-devel-list mailing list
> Mono-devel-list at lists.ximian.com
Marcos - http://www.youcannoteatbits.org
More information about the Mono-devel-list