Static reference nextDisplayable in Alert class hinders GC

[GoogleCodeExporter]

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

Original issue reported on code.google.com by bar...@gmail.com on 18 Nov 2009 at 11:43

[GoogleCodeExporter]

An alternative to making it an instance field would be to simply set it
null once it has been used.

Original comment by bar...@gmail.com on 18 Nov 2009 at 11:44

[GoogleCodeExporter]

Fixed in trunk (future 3.0 version)

Original comment by bar...@gmail.com on 8 Jan 2010 at 10:43

• Changed state: Fixed
• Added labels: Milestone-3.0

[GoogleCodeExporter]

Great, thanks!

Original comment by obensonne@googlemail.com on 8 Jan 2010 at 10:17

[GoogleCodeExporter]

Original comment by bar...@gmail.com on 9 Jan 2010 at 8:59

• Changed state: Verified