Hi Charles, On 2013-01-04, Charles Bouillaguet <charles.bouillag...@gmail.com> wrote: > There's also a (fixed) memory-leak : I am not sure if this can be doctested > properly…
Which memory leak do you mean? sage-5.6.beta2 contains a couple of fixes for memory leaks (#715). The fixes originally made some trouble (segfaults), but now seem to be fine, thanks to a bug fix in Cython (#13896). It could of course be the case that incidentally fixed other known leaks. Can you provide us with ticket numbers? And, by the way, memory leaks can be tested using get_memory_usage. Of course, the absolute memory usage is machine dependent. However, the fact that the memory usage does not increase during some computation should be machine independent. If the leak has to do with cyclic garbage collection (this is what #715 is about) then you could ask gc how many objects of a particular type it holds before and after some computation. Best regards, Simon -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To post to this group, send email to sage-devel@googlegroups.com. To unsubscribe from this group, send email to sage-devel+unsubscr...@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel?hl=en.
