#35: ./parrot with no args leaks memory
-------------------+--------------------------------------------------------
Reporter: coke | Owner:
Type: bug | Status: new
Priority: minor | Milestone:
Component: none | Version: trunk
Severity: low | Keywords: leak memory
Lang: | Patch:
Platform: |
-------------------+--------------------------------------------------------
Comment(by coke):
tools/dev/vgp runs parrot with --leak-test, the option that you're
referring to, so any thing that is still reachable at this point is an
issue.
However, if we assume that resources not released when we're generating
the usage message are ignorable, and instead only want to check the
smallest PIR program we can run, we can try with the PIR:
{{{
.sub n
noop
.end
}}}
tools/dev/vgp reports:
{{{
==13509== 8 bytes in 1 blocks are definitely lost in loss record 1 of 1
==13509== at 0x402601E: malloc (vg_replace_malloc.c:207)
==13509== by 0x4EA608F: strdup (strdup.c:43)
==13509== by 0x432A015: compile_to_bytecode (main.c:958)
==13509== by 0x432B380: imcc_run (main.c:1067)
==13509== by 0x8048977: main (main.c:60)
==13509==
==13509== LEAK SUMMARY:
==13509== definitely lost: 8 bytes in 1 blocks.
==13509== possibly lost: 0 bytes in 0 blocks.
==13509== still reachable: 0 bytes in 0 blocks.
==13509== suppressed: 0 bytes in 0 blocks.
}}}
This with r39769.
--
Ticket URL: <https://trac.parrot.org/parrot/ticket/35#comment:4>
Parrot <https://trac.parrot.org/parrot/>
Parrot Development
_______________________________________________
parrot-tickets mailing list
[email protected]
http://lists.parrot.org/mailman/listinfo/parrot-tickets
