#12215: Memleak in UniqueRepresentation, @cached_method
---------------------------------------------+------------------------------
Reporter: vbraun | Owner: rlm
Type: defect | Status: needs_work
Priority: major | Milestone: sage-4.8
Component: memleak | Keywords:
UniqueRepresentation cached_method caching
Work_issues: segfaults for elliptic curves | Upstream: N/A
Reviewer: | Author: Simon King
Merged: | Dependencies: #11115 #11900
---------------------------------------------+------------------------------
Comment(by SimonKing):
Fortunately, I now have a short example that triggers a memory access
error when leaving Sage:
{{{
sage: E = EllipticCurve('15a1')
sage: K.<t>=NumberField(x^2+2*x+10)
sage: EK=E.base_extend(K)
sage: EK.torsion_subgroup()
Torsion Subgroup isomorphic to Z/4 + Z/4 associated to the Elliptic Curve
defined by y^2 + x*y + y = x^3 + x^2 + (-10)*x + (-10) over Number Field
in t with defining polynomial x^2 + 2*x + 10
sage: quit
Exiting Sage (CPU time 0m1.98s, Wall time 0m52.03s).
local/bin/sage-sage: Zeile 303: 30045 Speicherzugriffsfehler sage-ipython
"$@" -i
}}}
However, I wonder how I can trigger the error without leaving Sage, and
how I can trace what is going on.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/12215#comment:20>
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.
