#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:
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 SimonKing):
Replying to [comment:199 nbruin]:
> If we could tell our `WeakValueDictionaries` something about their
codomain
Unfortunately, these aren't ''our'' `WeakValueDictionaries`, but Python's.
So, we can not.
> '''EDIT''': I guess a solution here could be to store a strong ref to
the gap interface on the object that needs gap comparison.
Sounds like a good idea.
Another one or two ideas:
1. We find out where that weak dictionary lives, and delete the whole
dictionary ''explicitly'' when Sage shuts down.
2. We find out where that weak dictionary lives, and if we are lucky then
we can replace it by a `MonoDict` or `TripleDict`.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/12313#comment:200>
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.
