#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:208 nbruin]:
> My bet is that this:
> {{{
> sage: search_src("WeakValueDict")
> ...
> rings/polynomial/pbori.pyx:255:rings = weakref.WeakValueDictionary()
> ...
> }}}
> is responsible for the SIGABRT in much the same way.
Funny that you name pbori.pyx! Meanwhile the doctests are finished, and I
got the error exactly there! And it is reproducible. Namely:
{{{
sage -t --verbose -force_lib "devel/sage/sage/rings/polynomial/pbori.pyx"
2342 tests in 280 items.
2342 passed and 0 failed.
Test passed.
*** glibc detected *** python: double free or corruption (!prev):
0x0000000007367de0 ***
}}}
and then htop shows me processes like
{{{
python /mnt/local/king/.sage/tmp/pbori_22813.py
python /mnt/local/king/.sage/tmp/mpc622-24779/pbori_9077.py
}}}
that are running at 0% CPU. Timeout, and again the error occurs when
shutting down Sage.
But that's good, because it is reproducible! And if pbori.pyx uses a weak
dictionary (I hope it wasn't I who introduced it...), it absolutely makes
sense to see an error there.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/12313#comment:209>
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.
