NEW MESSAGE: I got it: breadth_first_search (used in HasseDiagram.is_lequal) leaks.
if I use breadth_first_search(i, distance=self.cardinality()) instead, the leak is gone. Martin OLD MESSAGE: I just tried with python3. The code runs. check_bad3(7) allocates roughly 0.5 megabytes per invocation. check_bad3(6) also steadily allocates, but only about 0.1MB. check_bad3(5) even less. So, in fact, in python3 they all leak memory, if that's what a memory leak is. And I made a mistake in my previous message. The same is true for python2, but they leak much less memory. A few 100 runs are necessary so you see it for check_bad3(4), for example. However, as soon as I remove the call to moebius_function, the leak is gone. Martin -- 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 https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
