#12313: Fix yet another memory leak caused by caching of coercion data
--------------------------------------------------+-------------------------
Reporter: SimonKing | Owner:
Type: defect | Status:
needs_review
Priority: major | Milestone: sage-5.3
Component: memleak | Resolution:
Keywords: coercion weak dictionary | Work issues: Rebase wrt
the new version of #715. Take into account Nils' comments
Report Upstream: N/A | Reviewers: Simon King,
Jean-Pierre Flori, John Perry
Authors: Simon King, Jean-Pierre Flori | Merged in:
Dependencies: #11521, #11599, #12969, #12215 | Stopgaps:
--------------------------------------------------+-------------------------
Comment (by nbruin):
Some confusion on my part made me post possibly relevant note on the wrong
ticket: [http://trac.sagemath.org/sage_trac/ticket/11521#comment:152
#11521 comment 152]
Perhaps we should not be caching conversions at all, because they can too
easily cause memory leaks, for instance:
{{{#!python
for p in prime_range(1,1000):
k=GF(p)
a=k(1)
b=ZZ(a)
}}}
(the conversion maps get cached on `ZZ`, where the strong references to
the domains will keep the finite fields alive)
I'd think conversions are allowed to be expensive.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/12313#comment:138>
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.
