On 3 November 2012 19:58, Nils Bruin <nbr...@sfu.ca> wrote: > Presently, Sage has a significant memory leak issue: Uniqueness of > parents is currently guaranteed by keeping them in memory > permanently.
I've compiled Sage on Solaris with Sun libraries which replace malloc/free with versions which check for memory leaks. Sage has leaked memory before the sage: prompt has appeared. But from what I gather, one of the culprits does it own memory management, which would not be detected by those libraries. -- 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.
