On 25/6/14 19:57, Johan Brichau 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
ouch!
we will have to look at that. This is the problem that we do not have a
difference between loading code and incrementally compiling code.
May be this is the same that happened to me recently when I tried to do
((ConfigurationOfGlamour project version: #development) ignoreImage:
true; record), but sadly this is not the same :(
It reminds me a talk of Georg on VW showing that loading code in VW wa
spending 95% of the time in refreshing panes.
Can you open a bug entry with a high priority?
Is this a known issue? Any thoughts on what may be causing this?
regards!
Johan
