#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 jpflori):
I think the point of this ticket is exactly to solve the small example you
posted (which is nothing but what the ticket description suggests if I'm
not getting too tired):
* maps are cached in ZZ in a MonoDict which key is a weakref to k
* k dies, and the MonoDict is smart enough to let garbage collection
occurs.
The other way around (maps from ZZ to k, then k dies) should be trivial as
well.
Is that right?
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/12313#comment:139>
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.
