[Borges-users] current memory issues

[Kaspar Schiess]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Слепнев Владимир wrote:

| Borges keeps hogging my memory.
|
| 1) If we call() a component, then hit 'back', then call() it again,
| etc., memory grows unbounded. clear_delegate doesn't help.
|
| 2) If we set will_answer? of the component being called to false, the
| problem goes away. (This is a poor solution =)
|
| 3) In case (1), if we step out of a session.isolate() block, the memory
| does not get freed.
|
| This is bad. I can't seem to find the bug on my own. Anyone?
|
| Vladimir Slepnev

Hello Vladimir,

I was looking for it the last time you asked the question, but could not
find it either. I think that it somehow is logic to loose some memory
for a given period of time, since recalling repeatedly means recreating
stuff and snapshotting multiple branches. Where I loose the problem is
that I think that this stuff should get reclaimed by the gc, while it is
not. There must be a link to all these classes somewhere, blocking
things from being gc'ed.

I propose that we share our insights on the problem, trying to describe
what should happen and trying to find out what does not.

Second proposition: We need to develop a debugging toolkit for Borges.
That starts with the improvement of display in ObjectSpaceBrowser (which
can be very useful) and maybe even the creation of new tools.

Can you try to describe your model of the problem ?

best regards,
kaspar

code manufacture
www.tua.ch/ruby
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (MingW32)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFAkMogFifl4CA0ImQRAq4OAJ9b8gBVdDyA2j4lyqbbGWISq+rpcwCglMSF
duJ2tTHgKtuZ9dtDTEleSu8=
=wXsz
-----END PGP SIGNATURE-----