#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, #13145, to be merged with #11521 |
Stopgaps:
---------------------------------------------------------------------------+
Comment (by SimonKing):
When running sage-5.2.rc0 with patches on `OpenSuse` under gdb, I get the
following:
{{{
sage: @cached_function
....: def oddprime_factors(n):
....: l = [p for p,e in factor(n) if p != 2]
....: return len(l)
....:
sage: oddprime_factors.precompute(range(1,100))
Detaching after fork from child process 20030.
Detaching after fork from child process 20031.
...
Detaching after fork from child process 20127.
Detaching after fork from child process 20128.
sage:
}}}
If I understand correctly, that message comes from gdb and informs that
gdb can only follow one of the two processes after forking. So, that is to
be expected, right?
Anyway, it is another data point, telling that the two problems we are
seeing here are specific to OS X on Intel.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/715#comment:304>
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.
