#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 nbruin):
Replying to [comment:147 SimonKing]:
> I have updated the patch. Change: Before returning a value of the
dictionary or assert that a key is in the dictionary, I test whether the
keyed references involved are still active. If they are not, then the key
just happens to use the old memory location for new values.
So basically a `MonoDict` is now just a `WeakKeyDict` with identity
testing rather than equality testing. Unless sage parents have really bad
hash values, there should really not be a difference, right? That's one
thing to try. `TripleDict` still has its value, because of how it behaves
if any one of the key components disappears.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/12313#comment:148>
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.
