#12215: Memleak in UniqueRepresentation, @cached_method
--------------------------------------------------------------+-------------
Reporter: vbraun | Owner:
rlm
Type: defect | Status:
needs_work
Priority: major | Milestone:
sage-5.0
Component: memleak | Resolution:
Keywords: UniqueRepresentation cached_method caching | Work issues:
Keep the fix from #12313. Coercion in symmetric function algebras
Report Upstream: N/A | Reviewers:
Authors: Simon King | Merged in:
Dependencies: #11115 #11900 #12645 #11599 | Stopgaps:
--------------------------------------------------------------+-------------
Changes (by SimonKing):
* work_issues: Coercion in symmetric function algebras => Keep the fix
from #12313. Coercion in symmetric
function algebras
Comment:
I tested whether the problem comes from the combination of this ticket
with #12357. But it turns out that the following test
{{{
sage: K = GF(1<<55,'t')
sage: for i in range(50):
... a = K.random_element()
... E = EllipticCurve(j=a)
... P = E.random_point()
... Q = 2*P
sage: import gc
sage: n = gc.collect()
sage: from sage.schemes.elliptic_curves.ell_finite_field import
EllipticCurve_finite_field
sage: LE = [x for x in gc.get_objects() if isinstance(x,
EllipticCurve_finite_field)]
sage: len(LE) # indirect doctest
1
}}}
still fails. The test has been introduced in #12313. And of course it is
not acceptable that #12313 makes a memory leak disappear, but #12215 makes
it show up again.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/12215#comment:80>
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.
