Hi Simon! On Sunday, May 25, 2014 5:15:08 AM UTC-7, Simon King wrote:
So, it is a tiny amount of memory (~25 byte per round), but I guess it > should be fixed anyway. > I see a little more memory (~42 bytes). From such a small amount you can already guess no python objects get leaked, and indeed gc.get_objects() doesn't report anything unusual. I did try changing to a=f(1,1,0), [in that case a=0] and then no leak occurs! So my guess is a leak in libsingular (or our interface with/use of it), and it's only leaking on construction of non-zero values. Probably time to brush up your valgrind skills ... -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
