Samuel Lelievre
2018-12-04 07:55:51 UTC
Following the recent surge of interest in memory leaks, can people
with the relevant expertise revisit the open tickets on that theme:
check whether the leaks they report can still be observed, narrow
down their cause, fix them if possible?
Here is a Trac query revealing a number of such tickets.
https://trac.sagemath.org/query?desc=1&order=id&status=!closed&component=~leak&or&status=!closed&summary=~leak&or&status=!closed&keywords=~leak&or&status=!closed&description=~leak
with the relevant expertise revisit the open tickets on that theme:
check whether the leaks they report can still be observed, narrow
down their cause, fix them if possible?
Here is a Trac query revealing a number of such tickets.
https://trac.sagemath.org/query?desc=1&order=id&status=!closed&component=~leak&or&status=!closed&summary=~leak&or&status=!closed&keywords=~leak&or&status=!closed&description=~leak
--
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+***@googlegroups.com.
To post to this group, send email to sage-***@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.
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+***@googlegroups.com.
To post to this group, send email to sage-***@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.