Updates:
Status: Verified
Comment #15 on issue 185 by atdi...@gmail.com: Memory leak -
PActivityScheduler keeps processed activities in reference
http://code.google.com/p/piccolo2d/issues/detail?id=185
(No comment was entered for this change.)
--
Piccolo2D Developers Group:
Comment #12 on issue 185 by heue...@gmail.com: Memory leak -
PActivityScheduler keeps processed activities in reference
http://code.google.com/p/piccolo2d/issues/detail?id=185
Applied patch on trunk.
$ svn commit -m Issue 185 ; applying patch issue185fix.patch .
Committed revision 1085.
--
Updates:
Status: Fixed
Comment #14 on issue 185 by heue...@gmail.com: Memory leak -
PActivityScheduler keeps processed activities in reference
http://code.google.com/p/piccolo2d/issues/detail?id=185
Applied patch on release-1.3 branch.
$ svn commit -m Issue 185 ; applying patch
Comment #11 on issue 185 by nlskrg: Memory leak - PActivityScheduler keeps
processed activities in reference
http://code.google.com/p/piccolo2d/issues/detail?id=185
The ArrayList activities may be modified while iterating over
processingActivities, e.g., a finished activity is removed. I
Comment #10 on issue 185 by heue...@gmail.com: Memory leak -
PActivityScheduler keeps processed activities in reference
http://code.google.com/p/piccolo2d/issues/detail?id=185
Is there any reason that ArrayList processingActivities needs to exist at
all? Cannot processActivities iterate
Comment #7 on issue 185 by nlskrg: Memory leak - PActivityScheduler keeps
processed activities in reference
http://code.google.com/p/piccolo2d/issues/detail?id=185
The patch renders the first call of processingActivities.clear(); redundant
(in the same procedure the patch was applied to).
Comment #8 on issue 185 by atdixon: Memory leak - PActivityScheduler keeps
processed activities in reference
http://code.google.com/p/piccolo2d/issues/detail?id=185
Thanks, nlskrg, I agree. I code read your patch and it looks correct to me.
--
Piccolo2D Developers Group:
Updates:
Status: Started
Comment #9 on issue 185 by heue...@gmail.com: Memory leak -
PActivityScheduler keeps processed activities in reference
http://code.google.com/p/piccolo2d/issues/detail?id=185
Reopening per comments 7 8.
--
Piccolo2D Developers Group:
Comment #5 on issue 185 by atdixon: Memory leak - PActivityScheduler keeps
processed activities in reference
http://code.google.com/p/piccolo2d/issues/detail?id=185
Verified in trunk and release-1.3. Thanks!
--
Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en
Updates:
Status: Verified
Comment #6 on issue 185 by heue...@gmail.com: Memory leak -
PActivityScheduler keeps processed activities in reference
http://code.google.com/p/piccolo2d/issues/detail?id=185
(No comment was entered for this change.)
--
Piccolo2D Developers Group:
Updates:
Status: Fixed
Comment #4 on issue 185 by heue...@gmail.com: Memory leak -
PActivityScheduler keeps processed activities in reference
http://code.google.com/p/piccolo2d/issues/detail?id=185
Applied to trunk
$ svn commit -m Issue 185 ; applying patch from atdixon with minor
Updates:
Status: Accepted
Owner: heuermh
Labels: Type-Defect Priority-High Effort-Medium OpSys-All
Toolkit-Piccolo2D.Java Component-Core Milestone-1.3.1
Comment #2 on issue 185 by heue...@gmail.com: Memory leak -
PActivityScheduler keeps processed activities in reference
Comment #1 on issue 185 by atdixon: Memory leak - PActivityScheduler keeps
processed activities in reference
http://code.google.com/p/piccolo2d/issues/detail?id=185
Attaching patch that fixes 185.
Attachments:
Piccolo2D_Java_185.patch 542 bytes
--
Piccolo2D Developers Group:
13 matches
Mail list logo