On 2014-08-08, Nils Bruin <nbr...@sfu.ca> wrote: > ------=_Part_203_2052776100.1407511132909 > Content-Type: text/plain; charset=UTF-8 > > On Friday, August 8, 2014 3:02:03 AM UTC-7, Dima Pasechnik wrote: >> >> have a look at >> http://ecls.sourceforge.net/new-manual/re86.html#table.memory.limits >> and >> http://trac.sagemath.org/ticket/6772 >> where one of these limits was removed. >> Perhaps removing other limits will help. >> > > Actually, the change there did not make it into the maxima_lib interface > that calculus uses: > > sage: from sage.libs.ecl import * > sage: ecl_eval("(ext:get-limit 'ext:heap-size)") ><ECL: 1073741824> > > so doing > > sage: import sage.libs.ecl > sage: sage.libs.ecl.ecl_eval("(ext:set-limit 'ext:heap-size 0)") > > might solve your problem. I'm not sure if we should do the same. Since > maxima_lib runs in the same process as the rest of sage, it might be > problematic to let ecl munch away all memory and starve python (for > instance when a ulimit has been set). I don't think the boehm garbage > collector will ever "give back" once allocated memory to the operating > system.
if this is the case then how one would to to reclaim the memory? And why this is not a memory leak? Would at least restarting ecl release the memory? (it's not clear how the latter can be done; would maxima_calculus.reset() do the job?) -- You received this message because you are subscribed to the Google Groups "sage-support" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-support+unsubscr...@googlegroups.com. To post to this group, send email to sage-support@googlegroups.com. Visit this group at http://groups.google.com/group/sage-support. For more options, visit https://groups.google.com/d/optout.
