[Mono-dev] Leaky JIT while running MonoDevelop
vargaz at gmail.com
Thu Aug 14 19:24:21 EDT 2008
Try running the app with G_SLICE=always-malloc. That would force
glib to allocate all
memory using malloc, helping valgrind to produce more meaningful leak reports.
On Fri, Aug 15, 2008 at 1:22 AM, Casey Marshall
<casey.s.marshall at gmail.com> wrote:
> Rodrigo Kumpera wrote:
>> Hi Casey,
>> I have an idea on what might be the cause of the leak, and it only
>> happens under amd64 and aot.
>> Under amd64 mono_analyze_liveness2 is called from mono_analyze_liveness
>> if aot is enabled.
>> This will set MonoMethodVar::interval for a bunch of vars.
>> In mono_linear_scan, if ->internal is set it calls mono_linear_scan2 and
>> return. Notice that
>> mono_linear_scan release the supplied lists, "vars" and "regs", while
>> mono_linear_scan2 doesn't.
> I'm working from the mono-2-0 branch, and that doesn't have a
> mono_linear_scan2 function.
>> I don't have an amd64 setup here, but could you test if the following
>> change fix your issue:
>> Index: mono/mini/linear-scan.c
>> --- mono/mini/linear-scan.c (revision 110530)
>> +++ mono/mini/linear-scan.c (working copy)
>> @@ -509,4 +510,6 @@
>> g_list_free (active);
>> g_list_free (inactive);
>> + g_list_free (vars);
>> + g_list_free (regs);
> Mono-devel-list mailing list
> Mono-devel-list at lists.ximian.com
More information about the Mono-devel-list