Interesting! I sometimes notice the phenomenon of image growing and I suspected it has to do with the playground/inspector. We should investigate a memory leak related to announcements. I will try to look into this. Could you open an issue? This is a must fix for Pharo 4. Cheers, Doru On Fri, Feb 20, 2015 at 2:17 PM, Nicolai Hess <nicolaihess@web.de> wrote:
instances ?
If you open a fresh image and change the setting to use the old workspace open a workspace and execute: GTPlayground allInstances size -> 1
There is already one instance. I tried to get rid of this instance but I couldn't find a way. I think this instance is responsible for issue 14928 <https://pharo.fogbugz.com/default.asp?14928>: SystemNavigation default obsoleteClasses -> an Array(AnObsoleteGLMPageScroller AnObsoleteGLMPagerScrollMorph)
And this in turn, is repsonsible for undeleteable references to AnObsoleteKMUntypeableSingleKeyCombination. I need this for issue 14936 <https://pharo.fogbugz.com/default.asp?14936>
any idea?
nicolai
-- www.tudorgirba.com "Every thing has its own flow"