#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 nbruin):
Replying to [comment:258 SimonKing]:
> I am not totally sure if I understand what you mean: You say it would be
interesting to see the temporary file that is created by `sage -t`? Then:
see [attachment:failing_test_under_gdb.py].
>
> The original file was as in comment:251. It passes when running `sage
-t`, but fails when running `sage -t -gdb`.
But doctesting doesn't run it through `sage`. It executes `python
failing_test_under_gdb.py`. if I'm not mistaken. If you can run the exact
same command and input file that `sage -t` runs and not get a segv where
`sage -t` does, there is something really strange. I guess you might want
to control for environment variables as well, but other than that there
should really not be a difference.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/715#comment:261>
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.
