#13831: Upon quitting Sage, Maxima may keep running and eat up all memory
----------------------------------+-----------------------------------------
Reporter: nthiery | Owner: was
Type: defect | Status: new
Priority: major | Milestone: sage-5.6
Component: interfaces | Resolution:
Keywords: maxima orphans | Work issues:
Report Upstream: N/A | Reviewers:
Authors: | Merged in:
Dependencies: | Stopgaps:
----------------------------------+-----------------------------------------
Comment (by leif):
Replying to [comment:3 leif]:
> No idea yet what's really going on (i.e., what Maxima or ECL end up
doing), but apparently some Sage scripts indeed "get confused" (or behave
differently) when run from a `make` environment, probably then triggering
some Maxima bug.
Still no idea, but it doesn't seem related to environment variables (set
by `make`); the only ones that differ here are `MAKE`, `MAKEFLAGS`,
`MFLAGS` (the latter both empty), and `MAKELEVEL`. (And I can't reproduce
Maxima running mad with `env MAKE=... MAKEFLAGS="" MFLAGS="" MAKELEVEL=1
/path/to/sage -c '...'`.)
Wonder whether some file descriptors ''somehow^TM^'' get messed up...
(Although adding `print` to the Sage command line, the result is shown in
all cases; using e.g. `make -j1` doesn't make any difference. )
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/13831#comment:5>
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.
