#715: Parents probably not reclaimed due to too much caching
-------------------------------------------------------------------+--------
Reporter: robertwb |
Owner: somebody
Type: defect |
Status: needs_review
Priority: major |
Milestone: sage-5.4
Component: coercion |
Resolution:
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:
Dependencies: #9138, #11900, #11599, to be merged with #11521 |
Stopgaps:
-------------------------------------------------------------------+--------
Comment (by SimonKing):
I tried inserting print statements into
sage.parallel.use_fork.p_iter_fork._subprocess.
The print statements ''are'' executed when successfully running the
example in an interactive session.
They are ''not'' executed when running it interactively under gdb. Hence,
_subprocess (which contains the invalidation of pexpect interfaces) is not
involved in the interactive error under gdb.
They ''are'' executed when running the doctests. The test then fails
(because of the unexpected print statements), but there is no signal 11.
What could that mean? Perhaps we actually have two independent problems in
the same example: One appears in a gdb'ed interactive session and can be
fixed with #13437. The other appears with `sage -t` and remains a mystery.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/715#comment:253>
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.
