On Wednesday, May 11, 2016 at 8:15:50 AM UTC-7, Denis wrote: > > I wonder if the developers think this is a bug. From the user's point of > view it is certainly strange that one cannot invoke the same function call > twice in a row. > > Memory leaks are usually bugs, although in some cases, the caching behaviour that certain components of sage prescribe mean that what seems like a memory leak is in actuality according to specs.
Most memory leaks can be quite convincingly exhibited by running small cases in succession and showing that memory usage increases rather than stay roughly flat. Once you have such a case, finding what objects leak is usually fairly straightforward as well. How easy the fix is depends entirely ... If you can find a variant of your code that shows increased memory usage across many smallish cases where you expect flat memory use, it would really help if you could report it. Debugging a run that uses > 1Gb of memory is less likely to easily produce results. -- 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.
