#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):
Replying to [comment:257 nbruin]:
> Using `os.exit` versus `os._exit`: I can see why one might have thought
that's a good idea. We got what we came for (the function got executed and
the result is stored in an `.sobj` -- this should really be communicated
via a pipe to the parent, not via a temporary file), so why risk fouling
it up by doing more just to exit? However, if someone uses this for side-
effects (write to some shared file) it could be the buffers don't get
flushed. On the other hand, code is executing in parallel here (that's the
point), so one would probably already run into problems.
Changing `os._exit` into `os.exit` won't work. The example
`oddprime_factors.precompute(range(1,99))` seems to hang with that change.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/715#comment:260>
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.
