On Wed, Apr 23, 2008 at 3:55 PM, karl <karl.ramberg at comhem.se> wrote:
> Ties Stuij wrote:
>
> > On Mon, Apr 21, 2008 at 3:06 PM, Tomeu Vizoso <tomeu at tomeuvizoso.net>
> wrote:
> >
> >
> > >  Do you have any particular area in eToys that you would like to see
> > >  profiled, analyzed and maybe optimized?
> > >
> > >
> >
> > Yes! Of course ;o)
> >
> > Sorry for reacting so late on such an inviting mail.
> >
> > One of our most pressing problems has to do with continual image
> > growth, when opening multiple projects. After opening and closing
> > around 20 projects on an XO, the amount of memory the vm uses
> > (according to the vm stats), has climbed from 60 to 95 mb, and soon
> > afterwards we get an out of memory error.
> >
> > First I thought that old projects were lingering around, but they do
> > seem to be garbage-collected eventually. There is no reference or
> > pointer to them to be found in any case. I haven't had the time to do
> > any space profiling to see who or what could then be the cause of the
> > trouble.
> >
> >
>
>  I think there was a fix for this in the etoys 3.0 upadate stream.

That would be great! Any idea which fix?

>  Since you use your own image, epaati, you could just load all the projects
> and save the image with them loaded. You would have a giant image but
> switching would be quick. External projects is more a feature of etoys to
> make projects shareable and keep the image 'clean'.

Unfortunately the XO doesn't have enough ram to make that a feasable
solution in my experience.

/Ties