#715: Parents probably not reclaimed due to too much caching
------------------------+---------------------------------------------------
Reporter: robertwb | Owner: somebody
Type: defect | Status: needs_review
Priority: major | Milestone: sage-4.8
Component: coercion | Keywords: weak cache coercion
Work_issues: | Upstream: N/A
Reviewer: | Author: Simon King
Merged: | Dependencies: #9138, #11900
------------------------+---------------------------------------------------
Comment(by SimonKing):
One question: Currently, my patch uses weak references only for the first
two parts of the key. Should it also use weak references to the value,
when possible?
By "when possible", I mean that not all values allow weak references - if
it is possible then a weak reference is used, otherwise a strong reference
is used. This might contribute to fixing the memory leak in #11521, but it
might have a speed penalty.
Concerning #11521: The point is that an action (which currently does not
allow weak references, but that might change) has a strong reference to
the objects that are used for storing it in the cache. Hence, an action is
not collectable with the current patch.
Thoughts?
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/715#comment:32>
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.
