On Friday, December 22, 2017 at 3:07:13 AM UTC-8, Marco Caselli wrote: > > > > Il giorno lunedì 18 dicembre 2017 17:37:48 UTC+1, Nils Bruin ha scritto: >> >> If your routine f_ex runs out of memory then that would indicate a memory >> leak. If you look at the code for (K^6).__iter__ you'll see it really >> intends to be an iterator that uses limited memory. >> > > Yes, it is definitely a memory leak. Running the same routine on Magma I > have not experienced any memory issue. >
I can confirm that R.<x,y,z>=GF(3)[] f=x^2 + y^2 + z^2 + x + y + z - 1 while True: _=f.factor() does appear to be leaking memory. It's not leaking in python, though! If I compare the python heap before and after with gc.get_objects I'm not seeing any serious accumulation of objects. So the leak must be somewhere else; probably in the factorization library or the code interfacing with it. We have some leaking problems with libsingular, see e.g.: https://trac.sagemath.org/ticket/13447 https://trac.sagemath.org/ticket/15498 but this particular example doesn't seem to be exactly of the above reported kinds. -- You received this message because you are subscribed to the Google Groups "sage-support" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-support+unsubscr...@googlegroups.com. To post to this group, send email to sage-support@googlegroups.com. Visit this group at https://groups.google.com/group/sage-support. For more options, visit https://groups.google.com/d/optout.
