Begin forwarded message:
From: "Alain Rastoul"
<alr.dev(a)free.fr>
Date: June 26, 2011 6:43:58 PM GMT+02:00
To: pharo-project(a)lists.gforge.inria.fr
Subject: [Pharo-project] Moose out of memory
Reply-To: Pharo-project(a)lists.gforge.inria.fr
Hi,
There was a previous message in the list about an out of memory problem with
Moose when running
3 times MooseScripts createModelForConfigurationOfMoose
I downloaded moose suite 4.5 (Pharo 1.3) and played a bit with it reading
the moose book (nice).
IMHO although something is perhaps not completly clear in the vm in memory
allocation and/or ui process and/or low space watcher (I tryed to debug the
vm but did not succeed), here the problem seems to be in the Moose model.
I suspect that the problem is just that the cache keeps a reference to the
Moose model each time the script is run, see at the end of
MooseScripts>>createModelForConfigurationOfMoose the model is added to a
cache ((MooseModel root => MooseGroupRuntimeStorage>> byType) and takes abut
130M of memory each time.
clearing the Moose cache resolve the problem.
MooseModel allInstancesDo:[ :m | m remove ] seems to be working here, except
that there is an exception for the root model (I don't know Moose, it may
not be the best command).
Perhaps the moose model should not be added by type but overriden each time
(beeing identified by a "name" ?).
PS: Moose is cool :)
Cheers
Alain