[Mono-dev] Leaky JIT while running MonoDevelop
casey.s.marshall at gmail.com
Tue Aug 19 20:53:08 EDT 2008
On Tue, Aug 19, 2008 at 5:34 AM, Rodrigo Kumpera <kumpera at gmail.com> wrote:
> I spent a few hours yesterday trying to reproduce your bug without success.
> I have to say that from your valgrind result, the issue is closely related
> to how
> your perforce library interact with unmanaged code - it happens when you
> pass a delegate to a pinvoke and somehow memory is leaked.
Yeah, I'm willing to believe I'm doing something wrong with the
pointer-to-delegate handling, but it's also unfortunately not the
whole story -- it still leaks memory if I disable that code.
Valgrind's choosy about what it reports, I think, and I get different
leak reports on different runs, so it's super-hard to tell what the
underlying problem(s) is(/are).
> Do you mind sharing the code and say what exactly your code is calling so I
> can try to produce a repro? You can send it directly to me if you don't want
> to send it to
> a public mailing list.
We're probably going to release this as free software at some point,
but it isn't ready yet. The low-level stuff that's actually the
potential problem is a swig-generated wrapper around the Perforce C++
API. I can send you a copy of this, to spare the list a large
Sigh. Sorry about the noise.
More information about the Mono-devel-list