On Mon, Feb 4, 2019 at 11:41 AM E. Madison Bray <erik.m.b...@gmail.com> wrote: > > Anyone have any idea about this? > https://trac.sagemath.org/ticket/27213#comment:1 > > I don't know the code in this module at all so I'm totally in the dark > here. I don't understand why such a memory leak would occur, > particularly in such a narrow, difficult to reproduce case.
Well, the memory blow-up occurs when the process is forked to run palp in a subprocess. However, it occurs as soon as the fork() occurs. So this might be a Cygwin oddity. To be clear, this is not something that happens normally, so it is still bizarre. But at least this suggests that it's not just some memory leak in cause by code in Sage, at least I don't think. -- 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.
