On Apr 10, 2008, at 11:10 AM, Michael.Abshoff wrote: > > Brian Granger wrote: > > Hi Brian, > >>> Sure and it is certainly good to be discussed. I didn't want to be >>> dismissive about the idea, it is just that I have been in the >>> "debugging >>> memory leaks in Cython extension" trenches for the last eight >>> months and >>> hence I do not trust python or its memory management at all any >>> more. >>> And having been burned over and over again has left me the way I >>> am ;) >> >> Your comments make more sense in this light. Sounds painful :) >> >> Just our of curiosity - are the problem with cython itself or how >> people are using/misusing it? > > It is a general problem when writing extensions and Cython [via code > written by Robert Bradshaw] has started to add code to deal with the > situation. But the deallocation code can cause trouble when extensions > are carefully written (i.e. interdependencies) and I hope that during > Dev1 I will have time to delve into this.
To rephrase the problem, as the Python interpreter and environment get torn down, it becomes less and less safe to run the code invoked by deallocating objects. Most people don't worry about this because the whole process is about to be terminated, releasing all requested memory, but it does produce noise if one is trying to do memory profiling (e.g. with valgrind). - Robert --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-devel@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-devel URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
