On Thursday, May 31, 2018 at 9:24:57 AM UTC-7, Nils Bruin wrote: > > > > On Thursday, May 31, 2018 at 3:05:26 AM UTC-7, Erik Bray wrote: >> >> >> Could you actually point me to one of those memory leaks? I'm sure >> they exist but I'm still not clear on how this happens. I suspect it >> could be improved, and I would like to look into how... >> > > https://trac.sagemath.org/ticket/17008#comment:13 (prediction) > https://trac.sagemath.org/ticket/23851 > https://trac.sagemath.org/ticket/23807#comment:14 (explanation) > https://trac.sagemath.org/ticket/14549#comment:6 > https://trac.sagemath.org/ticket/18426 > https://trac.sagemath.org/ticket/14356 > https://trac.sagemath.org/ticket/17360 > https://trac.sagemath.org/ticket/18905#comment:26 > > The main thing that strikes me is how reasonable the code that introduces > the memory leak appears. That is why I expect this is a trap people will > keep falling in again and again. >
And to illustrate with what frequency you can expect to discover these things in our code base: https://trac.sagemath.org/ticket/25560 -- 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.
