Ticket #1765 (new bug) — at Initial Version
Memory leak in allocate_interpreter
Reported by: | nwellnhof | Owned by: | |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | core | Version: | trunk |
Severity: | medium | Keywords: | |
Cc: | Language: | ||
Patch status: | Platform: |
Description
$ valgrind --leak-check=full ./parrot t/op/interp_2.pir [...] ==22134== 789,400 (212 direct, 789,188 indirect) bytes in 1 blocks are definitely lost in loss record 1,075 of 1,075 ==22134== at 0x402328F: calloc (vg_replace_malloc.c:467) ==22134== by 0x40877B9: mem_sys_allocate_zeroed (alloc_memory.c:83) ==22134== by 0x4090788: allocate_interpreter (inter_create.c:124) ==22134== by 0x40908C8: make_interpreter (inter_create.c:92) ==22134== by 0x40DB6CC: create_interp (parrotinterpreter.pmc:183) ==22134== by 0x40DB7C8: Parrot_ParrotInterpreter_init (parrotinterpreter.pmc:252) ==22134== by 0x40BAB52: Parrot_pmc_new (pmc.c:164) ==22134== by 0x4069CC2: Parrot_new_p_sc (core_ops.c:20664) ==22134== by 0x40BBE74: runops_slow_core (cores.c:647) ==22134== by 0x40BB78D: runops_int (main.c:237) ==22134== by 0x409116C: runops (ops.c:127) ==22134== by 0x408D2D6: Parrot_pcc_invoke_from_sig_object (pcc.c:325) ==22134==
Note: See
TracTickets for help on using
tickets.