I tested your function on my Sage 4.7.alpha? install with 11468 (not 14468...) and 11495 and I do not seem tp get the leak: sage: leak() 0.46875 0.46875 0.46875 0.46875 0.46875 0.46875 0.46875 0.46875 0.46875 0.46875 0.46875 0.46875 0.46875 0.46875 0.46875 0.46875 0.46875 0.46875 0.46875 0.46875
On 25 juil, 10:16, Jean-Pierre Flori <jpfl...@gmail.com> wrote: > Ticket 11521 which seems to be nothing but 715 looks similar, but does > not seem related. > > You could also try applying 14468 and 11495 (patches but no reviews > yet, one is just a very old bug which has been unfortunately rolled > back). > They affect multi polynomial rings used by elliptic curves. > > Finally it might be worth having a look at 5949, but I would say it is > not related. > > On 25 juil, 09:55, Jonathan Bober <jwbo...@gmail.com> wrote: > > > > > > > > > I just found the following memory leak: > > > def leak(): > > K.<a> = NumberField(x^2 - x - 1) > > m = get_memory_usage() > > for n in xrange(100000): > > E = EllipticCurve(K, [3,4,5,6,7]) > > if n % 1000 == 0: > > print get_memory_usage() - m > > > sage: leak() > > 0.0 > > 0.5 > > 1.0 > > 1.0 > > 1.5 > > 2.0 > > 2.0 > > 2.5 > > 3.0 > > [...] > > > Is this the same as an already reported bug? It looks like it might be > > related > > tohttp://trac.sagemath.org/sage_trac/ticket/715orhttp://trac.sagemath.o...that > > this example is > > always constructing the exact same curve, and it isn't doing anything with > > it. If it isn't the same as those leaks, does anyone have any idea what it > > is? -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
