#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:
Work_issues: | Upstream: N/A
Reviewer: | Author:
Merged: | Dependencies:
------------------------+---------------------------------------------------
Comment(by SimonKing):
The idea sketched in the previous comment seems to work!!!
With it, after running
{{{
sage: for p in prime_range(10^5):
....: K = GF(p)
....: a = K(0)
....: print get_memory_usage()
}}}
ends with printing 825.45703125
Without it, it ends with printing 902.8125
I don't know if we should ban caching of field elements?
How could fixing that memory leak be demonstrated by a doc test?
Anyway, I will post a preliminary patch in a few minutes (so that you can
see if it fixes at least part of the problem for you), while I am running
`sage -tp 2 devel/sage`.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/11521#comment:25>
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.
