#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 think now I located the problem exposed by a gdb'ed interactive session.
When not redirecting stdout, a print statement before the last line of the
"finally:" clause of _subprocess is executed. But a print statement
inserted right after the call to `self._subprocess(f, dir, v[0])` in
`p_iter_fork.__call__` is not executed.
There is only one line of code between the executed and the not-executed
print statements: The last line of `_subprocess`' "finally:" clause,
namely
{{{
os._exit(0)
}}}
Question to the experts: What could possible go wrong in `os._exit(0)`?
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/715#comment:256>
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.
