#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):
Thank you for looking into the problem. I found that the problem seems to
be related with the doctest framework, too.
Namely, put the following into a file "test.py":
{{{
"""
sage: B.<a,b,c,d,e,f> = BooleanPolynomialRing()
sage: I = ideal(a*b + a + b*e + c*e + 1, a + b + c*d + c + 1,
a*c + c + d*f + d + 1, a*c + c*f + c + d*f + 1, c*f + c + d + e + 1, a +
b*c + b*d + e*f + 1)
sage: I.groebner_basis()
[1]
"""
}}}
The run sage -t on it. You will find the "glibc detected"
Then, run the same example interactively in Sage, and quit. Everything is
fine (or at least, it was for me.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/12313#comment:214>
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.
