From: Martin R. <fo...@ru...> - 2009-03-23 17:20:48
|
Dear fools again, I think I yesterday spotted the memory leak culprit. With Ramon's tests, I don't have a growing memory footprint anymore. 1. Anyway, this only seems to work when calling (collect) regularly -- if I don't call it, memory grows, even if the garbage collector kicks in from time to time (garbage-collect-notify? is #t). Is that normal for your elky scheme? Or just a kind of wrong information from top? 2. In Ramon's examples, he uses regularly (kill-context). I have the feeling that I asked this before: from the code, it looks whether there was not a "finaliser" function, which would clean all the objc-mess bound to a context on elk garbage collection. Also, a quick scan of the elk documentation did not enlighten me -- is this the reason why there is a (kill-context) at all? Ramon: would be great if you could try whether this solves the memory problems, maybe also with some more complex examples. All the best, m |