Dear Nadim, On 2019-02-12, Nadim Rustom <restom.na...@gmail.com> wrote: > Just to clarify, I didn't mean to ask whether #13447 itself is causing the > problem, I was just wondering if these problems were known and whether > #13447 was meant to fix the memory leak and speed problem. Thanks for your > efforts.
No problem. Indeed #13447 is a rather old ticket that has originally been intended to get rid of a permanent cache for polynomial rings (the attempt to change the permanent cache into a weak value dictionary previously resulted in segfaults). The old way to reference the underlying libsingular ring was quite inefficient (namely: Create a python object that is in one-to-one correspondence to the memory address of the libsingular ring and use that object as key in a dictionary that counts the references to that ring; so, for each change of refcount, an additional python object was created and deleted). Therefore, as a side effect of #13447, polynomial creation and deletion becomes faster. As Dima mentioned in his post, your first example got fixed as another side-effect, but your second didn't. So, I am opening a ticket now. Best regards, Simon -- 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.
