#11521: Memleak when resolving the action of Integers on an Elliptic Curve
------------------------+---------------------------------------------------
Reporter: jpflori | Owner: robertwb
Type: defect | Status: needs_info
Priority: major | Milestone: sage-4.8
Component: coercion | Keywords:
Work_issues: | Upstream: N/A
Reviewer: | Author:
Merged: | Dependencies:
------------------------+---------------------------------------------------
Comment(by SimonKing):
Without the patch:
{{{
sage: def test():
....: for p in prime_range(10^5):
....: K = GF(p)
....: a = K(0)
....:
sage: m0 = get_memory_usage()
sage: %time test()
CPU times: user 7.75 s, sys: 0.08 s, total: 7.83 s
Wall time: 7.84 s
sage: get_memory_usage() - m0
80.234375
}}}
With the patch:
{{{
sage: def test():
....: for p in prime_range(10^5):
....: K = GF(p)
....: a = K(0)
....:
sage: m0 = get_memory_usage()
sage: %time test()
CPU times: user 7.59 s, sys: 0.01 s, total: 7.60 s
Wall time: 7.61 s
sage: get_memory_usage() - m0
8.53515625
}}}
So, the memory does mildly increase, but it seems that most of the leak is
fixed.
I think that a test of the kind
{{{
sage: get_memory_usage() - -m0 < 10
True
}}}
might be used as a doc test.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/11521#comment:40>
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.
