S the memleak seems to be located within creation or rather coercing to MPolynomial_libsingular. Calling gc.collect() whithin the loop seem to fix or are least attenuate the problem. However, calling afterwards does not free memory back.
On 15 juin, 14:29, Jean-Pierre Flori <[email protected]> wrote: > Thanks a lot, I'll have a look at that. > > On 15 juin, 14:26, Alastair Irving <[email protected]> > wrote: > > > > > > > > > On 14/06/2011 21:58, Jean-Pierre Flori wrote: > > > > On 14 juin, 08:44, Simon King<[email protected]> wrote: > > >> Since sage-nt seems to agree that it is a bug, I opened trac ticket > > >> #11474. > > > Good ! > > > > About the original memleak, I tried looking at how > > > EllipticCurves_finite_field (maybe not correct name) are created but > > > could not find anything fishy, only Python code which should not > > > produce any memleak. > > > Hi > > > I think this is a problem with multivariate polynomials over finite > > fields and is not specific to elliptic curves. The following code > > produces a leak: > > > K=GF(2^50,"t") > > R.<x,y>=PolynomialRing(K) > > a=K.random_element() > > while(1): > > f=a*x > > del f > > > When constructing an elliptic curve its equation is constructed in the > > 3-variable polynomial ring over K, and thus we will get this leak. > > > Best wishes > > > Alastair -- To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/sage-support URL: http://www.sagemath.org
