#12313: Fix yet another memory leak caused by caching of coercion data
-------------------------------------------------+--------------------------
Reporter: SimonKing | Owner: rlm
Type: defect | Status: needs_review
Priority: major | Milestone: sage-5.0
Component: memleak | Resolution:
Keywords: coercion weak dictionary | Work issues:
Report Upstream: N/A | Reviewers: Simon King
Authors: Simon King, Jean-Pierre Flori | Merged in:
Dependencies: #715, #11521, #11599 | Stopgaps:
-------------------------------------------------+--------------------------
Comment (by jpflori):
FYI, make failed while building the doc because of lack of memory.
I allocated 1Go to the virtual machine, isn't it enough?
Looking at the memory consumption in top, it goes up to 65% (for the
python process alone, not counting other processes) at 98% of the "reading
source" stage and fails (on the last test it was at sage/notebook/twist).
Quite strangely, there was still some memory available, about 70 Mo at
least, not counting some memory cached, but the system might have refused
to allocate some more to the python process.
I think that's the only reason for the above failure on my side, and the
other ones I reported here (or in #715) on 32 bits.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/12313#comment:83>
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.
