#12313: Fix yet another memory leak caused by caching of coercion data
-------------------------------------------------+--------------------------
Reporter: SimonKing | Owner: rlm
Type: defect | Status: needs_work
Priority: major | Milestone: sage-5.0
Component: memleak | Resolution:
Keywords: coercion weak dictionary | Work issues:
Report Upstream: N/A | Reviewers:
Authors: Simon King, Jean-Pierre Flori | Merged in:
Dependencies: #715, #11599 | Stopgaps:
-------------------------------------------------+--------------------------
Changes (by SimonKing):
* status: needs_review => needs_work
Comment:
Too bad. With this ticket and its dependencies applied, I get at least
{{{
sage -t -force_lib "devel/sage/sage/structure/coerce_dict.pyx"
**********************************************************************
File
"/mnt/local/king/SAGE/stable/sage-5.0.beta10-gcc/devel/sage/sage/structure/coerce_dict.pyx",
line 735:
sage: len(LE) # indirect doctest
Expected:
1
Got:
50
**********************************************************************
File
"/mnt/local/king/SAGE/stable/sage-5.0.beta10-gcc/devel/sage/sage/structure/coerce_dict.pyx",
line 305:
sage: len(LE) # indirect doctest
Expected:
1
Got:
51
**********************************************************************
2 items had failures:
1 of 37 in __main__.example_19
1 of 39 in __main__.example_6
}}}
and the test suite isn't finished yet.
So, apparently the fixed memoy leak creeped back at a different ticket.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/12313#comment:47>
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.
