What was found then is that an explicit call to Python's garbage collector now and then was clearing the situation.
import gc gc.collect() L. Nathaniel Smith wrote: > I have some memory leak somewhere kicking my butt -- I'm running large > numbers of tests on a small cluster, and my slaves are falling over > and dying from the memory use -- and so my eye was caught by a > discussion on this list back in November about memory leak issues in > rpy2. I don't know yet whether it's rpy2 in particular that's causing > my problem, but it seems the most likely culprit at this point, so I > was wondering: are any memory leaks still known to exist in rpy2? And > if so, what is known about them now, as a starting point if I end up > going hunting for them myself? > > -- Nathaniel > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by: > SourcForge Community > SourceForge wants to tell your story. > http://p.sf.net/sfu/sf-spreadtheword > _______________________________________________ > rpy-list mailing list > rpy-list@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/rpy-list ------------------------------------------------------------------------------ This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword _______________________________________________ rpy-list mailing list rpy-list@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rpy-list
