#12313: Fix yet another memory leak caused by caching of coercion data
--------------------------------------------------------+-------------------
Reporter: SimonKing | Owner:
Type: defect | Status:
needs_work
Priority: major | Milestone:
sage-5.7
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, #13378 | Stopgaps:
--------------------------------------------------------+-------------------
Comment (by nbruin):
We've seen things like this before. This is exactly what one would see
from code that greatly benefited from rings (and hence their coercions!)
being nailed in memory. It's worth investigating whether there are some
obvious optimizations to make.
However, aren't `testsuites` made from automatic tests? In that case
wouldn't it be a very atypical mess of tiny little self-contained
constructions to test, e.g., commutativity, property of identity etc? We
shouldn't be optimizing code for those.
Otherwise just stick a strong cache in `DualSchurFunctions` somewhere.
That's such a specialized component that the memory leaking will likely
only affect those who know enough about the code to fix it once it's
necessary.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/12313#comment:281>
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.
