#12313: Fix yet another memory leak caused by caching of coercion data
-------------------------------------------------+--------------------------
Reporter: SimonKing | Owner:
Type: defect | Status: needs_work
Priority: major | Milestone: sage-pending
Component: memleak | Resolution:
Keywords: coercion weak dictionary | Work issues:
Report Upstream: N/A | Reviewers: Simon King,
Jean-Pierre Flori, John Perry, Nils Bruin
Authors: Simon King, Jean-Pierre Flori | Merged in:
Dependencies: #715, #11521, #12215, #13746 | Stopgaps:
-------------------------------------------------+--------------------------
Comment (by SimonKing):
* Can we be sure that `self.D` is not None when the `TripleDictEraser` is
called? Scenario: The `TripleDict` used to contain an object O. For some
reason, the `TripleDict` is part of a collectable reference cycle (hence,
the strong reference held by the `TripleDictEraser` would not prevent
deletion of the `TripleDict`), and gc decided to delete it first. Hence,
when calling the eraser, the `TripleDict` itself and not just its buckets
is already gone.
* Shouldn't the same be done with the `MonoDictEraser`?
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/12313#comment:268>
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.
