#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):
Alas. While running the tests, I accidentally saw
{{{
sage -t -force_lib devel/sage/sage/misc/preparser.py
[7.5 s]
sage -t -force_lib devel/sage/doc/en/thematic_tutorials/lie/crystals.rst
[5.8 s]
sage -t -force_lib devel/sage/sage/groups/group.pyx
[5.9 s]
sage -t -force_lib devel/sage/sage/rings/residue_field.pyx
[7.7 s]
*** glibc detected *** python: double free or corruption (!prev):
0x000000000757a7b0 ***
sage -t -force_lib devel/sage/sage/plot/animate.py
[4.5 s]
sage -t -force_lib devel/sage/sage/schemes/plane_curves/affine_curve.py
[6.5 s]
sage -t -force_lib devel/sage/sage/coding/source_coding/huffman.py
[4.2 s]
sage -t -force_lib devel/sage/sage/groups/abelian_gps/abelian_group.py
[4.6 s]
sage -t -force_lib devel/sage/doc/fr/tutorial/tour_algebra.rst
[7.6 s]
}}}
I give so much context, since I am running 4 tests in parallel. No idea
which of the tests results in the "glibc detected" being printed.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/12313#comment:205>
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.
