New issue 185 by atdixon: Memory leak - PActivityScheduler keeps processed
activities in reference
Piccolo's PActivityScheduler keeps activities in reference even after they
are processed. This also means that any state that activities reference
(nodes, e.g.) will also stay in reference and not get garbage collected.
This example demonstrates the problem:
This applies to Piccolo2d/Java, trunk and 1.3.
User group thread:
Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en