Hi! On Oct 25, 11:07 pm, Simon King <[EMAIL PROTECTED]> wrote: > At http://sage.math.washington.edu/home/SimonKing/f5/f5.pyx is the > latest version, i.e., the one with counters in __init__, __del__ and > __dealloc__ (which of course should eventually be removed).
Sorry, meanwhile I found that I was mistaken about __del__ versus __dealloc__: There is no __del__ method for extension types. My conjecture was that the memory leak was caused by (one of) the two extension types in my code. But now it seems that the problem is located somewhere else. At http://sage.math.washington.edu/home/SimonKing/f5/f5.pyx is the version with extension classes, and at http://sage.math.washington.edu/home/SimonKing/f5/f5B.pyx is essentially the same code with Python classes replacing the extension types. The memory leak is still present with Python classes. So, it seems to me that the leak might come from other compiled components. Libsingular? This is what I'm using most frequently. Valgrinding revealed a definite loss of 612 bytes and a potential loss of 394,644 bytes in two runs. See http://sage.math.washington.edu/home/SimonKing/f5/sage-memcheck.2402 Best regards Simon --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-support@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-support URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
