779 2013-07-11 05:05:07 +0200 NEWT: Use WeakReferences for Display, Screen and Window Caches 2013-07-11 05:05:58 +0200 1 1 3 JogAmp Newt core 1 All all RESOLVED FIXED --- enhancement --- 0 sgothel sgothel --- 99479bf3197cde8e89c5b499d135417863d521c7 d4c022b6b0fe7c3553c7ae218758d6e062905e10 --- oldest_to_newest 2796 0 sgothel 2013-07-11 05:05:07 +0200 Removing ref. at API destroy() is wrong ; Allow GC to clear .. - Removing ref. at API destroy() is wrong - Since all instances can be recreated, removing ref at destroy() is simply wrong. - Keep weak references until GC collects, i.e. user does not claim them anymore. - Safe for Display, since it holds it's EDT thread. - Window/Screen .. if user abandons reference .. nothing we can do here. - Allow GC to clear .. No need to hold ref loonger than user.