Issue 13: Static reference nextDisplayable in Alert class hinders GC
Status:  Verified
Owner:
Closed:  Jan 2010
Project Member Reported by bar...@gmail.com, Nov 18, 2009
First of all, thank you for MicroEmulator .. living alone with WTK would be
a PITA.

Now to the issue, the title says it already. The static reference is not
really a leak, as this reference gets refreshed when a new Alert is
displayed so that finally the previous object referenced by
Alert.nextDisplayable may get garbage collected. However this reference
makes profiling for real memory leaks complicated. Things would be easier
if this reference would be an instance field.

Thanks and cheers,
Oben

BTW.. I'm using MicroEmu 2.0.3


Nov 18, 2009
Project Member #1 bar...@gmail.com
An alternative to making it an instance field would be to simply set it
null once it has been used.
Jan 8, 2010
Project Member #2 bar...@gmail.com
Fixed in trunk (future 3.0 version)
Status: Fixed
Labels: Milestone-3.0
Jan 8, 2010
#3 obensonne@googlemail.com
Great, thanks!
Jan 9, 2010
Project Member #4 bar...@gmail.com
(No comment was entered for this change.)
Status: Verified