Sorry to ask then, but:
would it be possible to profile a configurationOf... load with and
without a Nautilus open? Time spent handling announcements should be
visible, and, yes, when loading code, Browsers have to be aware the code
is being changed.
I spent some time optimizing that for AltBrowser, and it can very
significantly increase the loading time, without counting in side
effects such as over-caching (and I know Nautilus does some caching, but
I'm not sure I understand why).
Thierry
Le 25/06/2014 20:20, [email protected] a écrit :
Maybe due to some Annoucement being picked up by Nautilus?
Phil
On Wed, Jun 25, 2014 at 7:57 PM, Johan Brichau <[email protected]
<mailto:[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
--
Thierry Goubier
CEA list
Laboratoire des Fondations des Systèmes Temps Réel Embarqués
91191 Gif sur Yvette Cedex
France
Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95
