The gap session to which sage communicates is started by default with the option -o 9999G set. This means that, if gap uses all the memory it won't return an error message, but will be killed by the OS. The sage session continues, with an error message, but there would be "orphan" objects that point to gap objects that no longer exist.
If the -o option would be set by sage depending on the available memory in the system (and OS limits to its use by a a program), this wouldn't happen: gap would give an error, but the session would persist. So no orphan objects. What do you think? -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
