#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: Speed
regression
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 jpflori):
Replying to [comment:287 nbruin]:
> Perhaps follow up speed regressions on #13991? Once it's clearer what
the problem is, we can decide if that ticket should be a dependency for
this one. Obviously, if it turns out to be a design flaw there, we
shouldn't hold the rest of sage hostage to its resolution. The problem
addressed by this ticket is a real one.
I'd prefer this approach as well, being more affected by the cache
problems than by the schur things I don't use.
And I assume this should be the case of the majority of users.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/12313#comment:288>
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.
