petdance/scratch — Issue #329: Memory leak in allocate_interpreter
Author: petdance
Created: 2011-11-01 05:42:03+00:00
State: open
Labels: bug, core, Pri-normal, Sev-medium

{{{
$ valgrind --leak-check=full ./parrot --leak-test t/op/interp_2.pir
[...]
==4748== 131,364 (216 direct, 131,148 indirect) bytes in 1 blocks are definitely lost in loss record 184 of 184
==4748== at 0x402328F: calloc (vg_replace_malloc.c:467)
==4748== by 0x40F262B: mem_sys_allocate_zeroed (alloc_memory.c:82)
==4748== by 0x4108184: allocate_interpreter (inter_create.c:123)
==4748== by 0x410813A: make_interpreter (inter_create.c:91)
==4748== by 0x416FFED: create_interp (parrotinterpreter.pmc:182)
==4748== by 0x41708C8: Parrot_ParrotInterpreter_init (parrotinterpreter.pmc:251)
==4748== by 0x413BCAB: Parrot_pmc_new (pmc.c:163)
==4748== by 0x40B8F13: Parrot_new_p_sc (core_ops.c:20494)
==4748== by 0x413E780: runops_slow_core (cores.c:646)
==4748== by 0x413D7F9: runops_int (main.c:218)
==4748== by 0x41098EE: runops (ops.c:126)
==4748== by 0x4103CCA: Parrot_pcc_invoke_from_sig_object (pcc.c:323)
}}}

Originally http://trac.parrot.org/parrot/ticket/1765