#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 jpflori):
If you used "==" for equality testing for actions in the coercion model
(as in the parent caches) and let "j=j" in the "usual piece of code", this
is not surprising because for "==" all the curves are equal, so there will
be no duplication nor memory leak.
To perform a better test, you should replace j=j by j=K.random_element()
in the constructor of the elliptic curve (as I did a few tickets up) to
get really different curves (i.e. for "is" and for "==").
I fear the memory leak is still there with this second example...
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/11521#comment:105>
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.
