Menu
▾
▴
2 Attachments
#3288 Maxima is dead in the water on the MacOS after Apple security update.
I use Maxima almost every day. As of a week ago Maxima is dead in the water on the MacOS Platform running El Capitan. I have redownloaded most recent version, scrubbed and cleaned and I get a reproducible Maxima crash with the attached error log. and .wxm file that contains only two lines kill(all)$ and 2+2;
All other codes on this machine function properly. It is also stable otherwise. I downloaded Apple security updates and the problem started around the time of that update. Recent versions of MacOS have protected certain directories that were formerly available for install. My instinct is that some access to these formerly open directories is the cause of the crash.
After each Maxima crash, a common lisp process 'sbcl' is left running on the machine and this process has very high CPU utilization. If not detected several of these processes taken together can overheat some machines, Stuxnet style. I have to keep on an icepack to keep the CPU temperature below 210 degrees. Bringing up the activity manager or doing a ps -au shows the zombie common lisps which can be killed one at a time.
It appears from the log file you posted that wxMaxima has crashed (with a segfault).
Does command line Maxima work OK?
I'm closing this report as it appears to be a wxMaxima problem on the basis of the evidence so far. I have opened a new issue on the wxMaxima bug tracker: https://github.com/andrejv/wxmaxima/issues/858
This item can be reopened if it turns out to be a Maxima problem after all. In the meantime please direct further discussion to the wxMaxima issue.
Command Line Maxima works.
2+2; works
running more than a four line program crashes, see attached text file which can be transferred to wxMaxima bug tracker.