Maybe due to some Annoucement being picked up by Nautilus? Phil
On Wed, Jun 25, 2014 at 7:57 PM, Johan Brichau <[email protected]> wrote: > Hi, > > It seems that when even a single Nautilus system browser is open and you > do a load (using Metacello), there is a huge amount of objects that get > created and persisted in the image. > This even leads to the point that the image crashes when I try to load our > code using a ConfigurationOf. After some time, the Pharo process is stuck > at 100%, image size is over 500MB and the entire image becomes > unresponsive, finally crashing after an hour or so. > > I have not yet found which objects or why, but I just wrestled with this > all day to find out what was going on. I first thought that Metacello was > in an infinite loop but after noticing that the image was so large (500MB) > and that it got reduced to 20% of its size after closing the browser > window, I can say that Nautilus is gathering garbage. It is definitely not > Metacello because I can trigger the same problem doing a load via > Monticello only. > > When I load the ConfigurationOf without a single browser open, it loads 5x > faster and the image size stays reasonable. > > Is this a known issue? Any thoughts on what may be causing this? > > regards! > Johan >
