Hi Simon, On Jan 4, 2013, at 2:59 PM, Simon King wrote:
> 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? http://trac.sagemath.org/sage_trac/ticket/9298 I don't know if it is related to #715... > And, by the way, memory leaks can be tested using get_memory_usage. I was afraid of writing a dockets such a : sage: x = get_memory_usage() … do crazy stuff … assert x == get_memory_usage() Isn't this likely to raise false positives sometimes? --- Charles Bouillaguet http://www.lifl.fr/~bouillaguet/ -- 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.
