From: Pierre S. <p.s...@gs...> - 2008-06-11 07:37:48
|
Dear Nor, thanks for your bug report. I found the error and fixed it in CVS. I use this module frequently but not in such loops and did not yet bump into it. (The source of the error was a wrong swig typemap name). It is fixed in CVS. A snapshot is uploaded to: http://pygsl.sf.net/pygsl-0.9.3.tar.gz Please can you tell me if it fixes the problem for you? Dear All, please could you tell me if it introduces new problems? Sincerely yours Pierre > Hi, > > There seems to be a nasty memory leak in the interpolation module. It > is as if data are not properly freed after a spline object is not > longer use. > You can test this by running this snippet of code. This has been > happening for a while now and I am wondering if there was a patch for > this problem or whether a fix was being planned? > In the following example, the ram used by the script increases by > about 2meg per sec... > > from pygsl import spline > from numpy import * > > def t(): > a = arange(100) > b = arange(100) > fctmu = spline.linear(len(a)) > fctmu.init(a,b) > c = arange(100) > > t = map(fctmu.eval,c) > > > for i in range(100000): > print "i:",i > t() > > Cheers, > Nor > > > > ------------------------------------------------------------------------- > Check out the new SourceForge.net Marketplace. > It's the best place to buy or sell services for > just about anything Open Source. > http://sourceforge.net/services/buy/index.php > _______________________________________________ > pygsl-discuss mailing list > pyg...@li... > https://lists.sourceforge.net/lists/listinfo/pygsl-discuss |