#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 SimonKing):
Replying to [comment:245 nbruin]:
> YES! All tests pass for me too. I think the saying is "Mission
Accomplished".
>
> Concerning speed effects:
>
> 5.3b2 + (#715, #11521, #12215, #12313):
> {{{
> Total time for all tests: 1001.4 seconds
> Total time for all tests: 1002.6 seconds
> }}}
>
> plain 5.3b2:
> {{{
> Total time for all tests: 928.5 seconds
> Total time for all tests: 932.6 seconds
> }}}
That is almost 8% regression. That isn't good. Can you find out what tests
contribute most to the regression?
When I hacked into the weakref module for debugging, I found that many
weak references die ''during startup'' of Sage. Hence, while Sage starts,
many things are created without keeping a reference to them, so that they
will be garbage collection before the user has even the chance to see
them. I think it would be good (also for Sage startup time) to avoid that
to happen. But I reckon this should be on a new ticket.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/12313#comment:247>
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.
