Hi Andreas,
On Thu, 23 Apr 2009 05:41:09 pm Andreas Ericsson wrote:
> Ishwor Gurung wrote:
> > Hi list,
> >
> > Whats an appropriate way to check for memory leak of a mono application?
> >
> > I googled around with some example using valgrind for mono app but
> > couldn't find any concrete example
On Thu, Apr 23, 2009 at 5:29 PM, Mike Christensen wrote:
> The .NET world has all sorts of great tools like SOS/Windbg as well as all
> sorts of third party analysis. Is there anything in the Mono world to help
> out with this?
If you're asking for what I think you are, then you probably want to
I guess this really depends on what you mean by a memory leak.. If you mean
the object is not reachable and on the queue to be garbage collected, one
might "just trust the GC". However, there's also a lot of value on being
able to see what objects are on the heap (and large object heap), what
gen
Ishwor Gurung wrote:
> Hi list,
>
> Whats an appropriate way to check for memory leak of a mono application?
>
> I googled around with some example using valgrind for mono app but
> couldn't find any concrete examples. What I've essentially done so far
> using valgrind is:
> $ valgrind --tool=mem
Hi Rodrigo,
Rodrigo Kumpera wrote:
> Hi,
[ ... ]
> Valgrind is the best too to dig for memory leaks. But it will only report
> problems of
> unmanaged memory leaks. For managed memory, just trust the GC.
Right.
> Mono is supposed to do a clean shutdown, but we still have some small
> non-impor
Hi,
On Wed, Apr 22, 2009 at 8:52 PM, Ishwor Gurung wrote:
> Hi list,
>
> Whats an appropriate way to check for memory leak of a mono application?
>
> I googled around with some example using valgrind for mono app but
> couldn't find any concrete examples. What I've essentially done so far
> using
Hi list,
Whats an appropriate way to check for memory leak of a mono application?
I googled around with some example using valgrind for mono app but
couldn't find any concrete examples. What I've essentially done so far
using valgrind is:
$ valgrind --tool=memcheck --leak-check=full --show-reacha
