#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:270 nbruin]:
> Replying to [comment:269 SimonKing]:
> If
> {{{
> $ sage -sh
> ...
> > python -t failing_test_under_gdb.py
> }}}
> is giving you a segfault,
It isn't. As I stated above, with the short test file written down in
comment:251 I can reproduce the failure occurring with `sage -t -gdb`, but
it passes with `sage -t`. And so does its pure python version.
In other words, I'll now try to get the python version of the full test of
cachefunc.pyx.
> perhaps you can get that to dump core? (if I send
> `kill -11 [python process]` I get a core dumped if I unset the limit).
Could you elaborate more? By `[python process]` you mean the pid of the
test, right? How can I find out the pid in the few seconds that the test
takes before failing?
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/715#comment:271>
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.
