#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:175 jpflori]:
> I agree.
> I'm only pointing out that on at least one computer, the speed
regression, which had to be expected, seems more than negligible to me and
should definitely not be taken into account for the inclusin of these
tickets.
If someone is really interested in tracking down where the speed
regression is coming from, they could sprinkle parents with an "elixir of
life". I think it would be enough to patch `UniqueRepresentation` with a
global list to which any newly created structure gets appended. That
should bless all parents with eternal life and hence make all our weak
caching permanent once again.
Code that significantly benefits from this elixir should be marked for
restructuring. It should keep better track of what parents it reuses. It's
unrealistic to expect that the system is clairvoyant in this matter.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/12313#comment:176>
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.
