#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 undecided what we should do:
We could argue that my patch does fix some memory leak, and leave it like
that (modulo comments of the reviewer, of course). In order to fix the
memory leak exposed by the example from the ticket description, we have no
chance but to have some kind of uniqueness for elliptic curves. But that
is a different topic and should thus be dealt with on a different ticket
(perhaps such ticket already exists?).
Or we could argue that this ticket is about fixing the memory leak that is
exposed in the description. Hence, we should do all necessary steps
''here''.
And then, there is still the question whether the number theorists really
want the elliptic curves be "weakly unique" (i.e., identical if the given
data are equal). In addition, we might want that the elliptic curve cache
is weak - which might imply that we have to wait for #12215.
What do you think?
I guess I'll also ask on sage-nt.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/11521#comment:66>
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.
