Comment #4 on issue 74 by allain.lalonde: Memory leak with
PSwingRepaintManager
http://code.google.com/p/piccolo2d/issues/detail?id=74
heuermh has suggested an alternative fix that's impressive in it's elegance.
It seems possible to do away with the swingWrappers entirely, this would
Comment #5 on issue 74 by heuermh: Memory leak with PSwingRepaintManager
http://code.google.com/p/piccolo2d/issues/detail?id=74
Committing an example that attempts to demonstrate the leak. The behaviour
with or
without the fix Allain alluded to before doesn't appear any different to
me.
Comment #6 on issue 74 by heuermh: Memory leak with PSwingRepaintManager
http://code.google.com/p/piccolo2d/issues/detail?id=74
For what it's worth, used memory is not reclaimed when PSwingCanvases are
removed
with the original patch too. Perhaps the example is flawed.
--
You received this
Comment #7 on issue 74 by allain.lalonde: Memory leak with
PSwingRepaintManager
http://code.google.com/p/piccolo2d/issues/detail?id=74
Although I think the memory leak identified above is a problem.
It's not the only one. Turns out that the memory leak exists in PCanvas,
not just
Comment #8 on issue 74 by allain.lalonde: Memory leak with
PSwingRepaintManager
http://code.google.com/p/piccolo2d/issues/detail?id=74
heuermh's elegant solution I referred to above is attached. It basically
amounts to
removing the need for tracking PSwingCanvas.SwingWrapper instances in
Comment #9 on issue 74 by allain.lalonde: Memory leak with
PSwingRepaintManager
http://code.google.com/p/piccolo2d/issues/detail?id=74
Committed changes, test passes in Eclipse, doesn't pass on the command line
or when
being run from Hudson. *Very stange*
--
You received this message
Comment #3 on issue 74 by allain.lalonde: Memory leak with
PSwingRepaintManager
http://code.google.com/p/piccolo2d/issues/detail?id=74
I'd go with applying the patch until we have a better solution. Working is
working.
I'll make the changes if someone else agrees.
--
You received this
