#11521: Memleak when resolving the action of Integers on an Elliptic Curve
------------------------+---------------------------------------------------
Reporter: jpflori | Owner: robertwb
Type: defect | Status: needs_work
Priority: major | Milestone: sage-4.8
Component: coercion | Keywords: sd35
Work_issues: | Upstream: N/A
Reviewer: | Author: Simon King
Merged: | Dependencies: #11900 #715
------------------------+---------------------------------------------------
Comment(by SimonKing):
I am not sure whether we should really stop work right there. After all,
it is still not 100% clear to me why the elliptic curve E, that is created
in the loop in an increasing number of copies, can not be garbage
collected.
First, E is created, and some coercion into it is created. The coercion is
cached. By #715, some key of the cache provides a weak reference to E. In
addition, the coerce map refers to a homset, and the homset refers to its
codomain, which is E. I wonder whether there is a chain of strong
references from E to the homset (one could try to find out using objgraph,
I guess). If there is, then we would have a reference cycle. If that was
the case, then we needed to find a `__del__` method that prevents the
cycle from being garbage collected.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/11521#comment:69>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/sage-trac?hl=en.
