On 14 juin, 08:44, Simon King <simon.k...@uni-jena.de> 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. I also tried running sage under valgrind (using the new spkg available on trac) but that was not more helpful. So any help or advice, even completely trivial, to investigate this would be welcome. Cheers, JP -- To post to this group, send email to sage-support@googlegroups.com To unsubscribe from this group, send email to sage-support+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-support URL: http://www.sagemath.org
