#715: Parents probably not reclaimed due to too much caching
--------------------------------------------------------------------+-------
Reporter: robertwb |
Owner: somebody
Type: defect |
Status: closed
Priority: major |
Milestone: sage-5.5
Component: coercion |
Resolution: fixed
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: sage-5.5.beta0
Dependencies: #13145, #13741, #13746, to be merged with #11521 |
Stopgaps:
--------------------------------------------------------------------+-------
Comment (by vbraun):
The first line is the error, like "Invalid read of size 8" = the code
wants to read 8 bytes from a location that it is not on the stack or
hasn't been malloc'ed. Then follows the stack backtrace, first the
function that caused the error then the calling function etc (just like
gdb).
Valgrind will keep info about the most recent free's to give you a better
diagnostic (this has been freed previously and you are this far into the
freed space) but it won't track all frees that have ever happened (which
would be prohibitive ram usage). There are some options to control this,
for example
{{{
--freelist-vol=<number> volume of freed blocks queue
[20000000]
--freelist-big-blocks=<number> releases first blocks with size >=
[1000000]
}}}
see also `valgrind --help`
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/715#comment:349>
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.