#13211: Upgrade GAP to 4.5.6
------------------------------------------------------------------+---------
Reporter: kini |
Owner: tbd
Type: enhancement |
Status: needs_work
Priority: major |
Milestone: sage-5.6
Component: packages |
Resolution:
Keywords: | Work
issues:
Report Upstream: Reported upstream. Developers acknowledge bug. |
Reviewers: Dmitrii Pasechnik
Authors: Volker Braun | Merged
in:
Dependencies: #13123, #13579 |
Stopgaps:
------------------------------------------------------------------+---------
Comment (by dimpase):
Replying to [comment:191 vbraun]:
> If you don't specify '-o' then gap will just chose a pool size for you.
The virtual memory pool address space can't be changed after GAP has
started. The actual memory used can expand and contract. Of course the
actual memory used is bounded by the pool size.
OK. Still, what about limiting the suggested_size to something (say,
500MB) - I agree that 150MB I suggested above is on a low side.
Anyway, we should put somewhere in the documentation a remark that by
default such-and-such max amount is allocated, but if you need more, then
do {{{set_gap_memory_pool_size()}}} before doing any GAP stuff.
By the way, can one terminate, from Sage, all the running GAP
subprocesses?
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/13211#comment:192>
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.
