[MonoDevelop] Memory leak
m.j.hutchinson at gmail.com
Thu Aug 14 13:59:14 EDT 2008
On Thu, Aug 14, 2008 at 1:44 PM, Casey Marshall
<casey.s.marshall at gmail.com> wrote:
> Yeah, somehow MD is putting pressure on the JIT, and it's not reclaiming a
> lot of storage. I ran MD again overnight, this time with
> --optimization=-linears (this was where the original valgrind trace came
> from) and the memory usage grew much more slowly. The big-huge trace I found
> in the valgrind output this morning was a different location in the JIT:
>> ==5807== 794,797,632 bytes in 1,601,948 blocks are still reachable in loss
>> record 238 of 238
>> ==5807== at 0x4C21F8F: memalign (vg_replace_malloc.c:460)
>> ==5807== by 0x4C22028: posix_memalign (vg_replace_malloc.c:569)
>> ==5807== by 0x507D299: (within /usr/lib/libglib-2.0.so.0.1600.4)
>> ==5807== by 0x507E0F0: g_slice_alloc (in
>> ==5807== by 0x506035D: g_list_prepend (in
>> ==5807== by 0x52AF25: mono_allocate_stack_slots_full (mini.c:9812)
>> ==5807== by 0x432320: mono_arch_allocate_vars (mini-amd64.c:1137)
>> ==5807== by 0x558127: mini_method_compile (mini.c:12525)
>> ==5807== by 0x559419: mono_jit_compile_method (mini.c:12836)
>> ==5807== by 0x42C5E2: mono_magic_trampoline (mini-trampolines.c:249)
>> ==5807== by 0x415B164: ???
>> ==5807== by 0x8BA4AAB: ???
> I don't think valgrind captures absolutely everything, so the above might
> have contributed to the earlier case, too.
> I'll send a message to the mono-devel list.
BTW, it looks like it's possible to get names for those two ?? items:
More information about the Monodevelop-list