#715: Parents probably not reclaimed due to too much caching
----------------------------------------------------+-----------------------
Reporter: robertwb | Owner: somebody
Type: defect | Status: closed
Priority: major | Milestone: sage-5.5
Component: coercion | Resolution: fixed
Keywords: weak cache coercion Cernay2012 | Work issues:
Report Upstream: N/A | Reviewers:
Jean-Pierre Flori, Simon King, Nils Bruin
Authors: Simon King, Jean-Pierre Flori | Merged in:
sage-5.5.beta0
Dependencies: #13145, to be merged with #11521 | Stopgaps:
----------------------------------------------------+-----------------------
Comment (by jpflori):
Got a segfault in interrupt.pyx during "make ptestlong" on 5.5.rc0 plus
the fixes mentioned above plus some pynac related patches.
I got
{{
Fatal Python error: GC object already tracked
}}
followed by an highly uninterresting backtrace involving Python magic
(from libpython itself and the Sage process and doctesting environment I
guess), interrupt.so, a final call to PyTuple_New in libpython and boom
(through libpthread and libcsage), but in particular nothing related to
pynac, so the additional patches concerning pynac can be ruled out.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/715#comment:337>
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.
