MATLAB: Does MATLAB crash when I try to close it using the Dock while MATLAB is starting

#seecommentsformoreinfo#segvpilotMATLAB

When I try to close MATLAB R2009b from the Mac Dock while MATLAB is trying to start, MATLAB crashes resulting in the following stack trace:
Stack Trace:
  [0] libmwmcr.dylib:mcrInstanceInternal::PushInterpreterState(bool) + 123 bytes
  [1] libmwmcr.dylib:AutoInterpreterState::AutoInterpreterState(mcrInstance*, bool) + 48 bytes
  [2] libmwmcr.dylib:mnShutdownMatlabInternal(bool, bool, bool) + 166 bytes
  [3] libmwmcr.dylib:mnFullExitFcn(int, mxArray_tag**, int, mxArray_tag**) + 107 bytes
  [4] libmwm_dispatcher.dylib:Mfh_builtin::dispatch_mf(int, mxArray_tag**, int, mxArray_tag**) + 84 bytes
  [5] libmwm_dispatcher.dylib:Mfh_MATLAB_fn::dispatch_fh(int, mxArray_tag**, int, mxArray_tag**) + 215 bytes
  [6] libmwm_interpreter.dylib:inDispatchFromStack(int, char const*, int, int) + 1030 bytes
  [7] libmwm_interpreter.dylib:inDispatchCall(char const*, int, long, int, int*, int*) + 166 bytes
  [8] libmwm_interpreter.dylib:inInterp(inDebugCheck, int, int, opcodes, inPcodeNest_tag volatile*, long*) + 4813 bytes
  [9] libmwm_interpreter.dylib:protected_inInterp(inDebugCheck, int, int, opcodes, inPcodeNest_tag*, long*) + 140 bytes
  [10] libmwm_interpreter.dylib:inInterPcodeSJ(inDebugCheck, int, int, opcodes, inPcodeNest_tag*, long*) + 265 bytes
  [11] libmwm_interpreter.dylib:inInterPcode + 125 bytes
  [12] libmwm_interpreter.dylib:inEvalStringWithIsVarFcn(_memory_context*, char const*, EvalType, int, mxArray_tag**, inDebugCheck, _pcodeheader*, int*, bool (*)(void*, char const*), void*, bool, bool) + 2511 bytes
  [13] libmwm_interpreter.dylib:inEvalCmdWithLocalReturn(char const*, int*, bool, bool, bool (*)(void*, char const*)) + 145 bytes
  [14] libmwm_interpreter.dylib:InterpBridge::EvalCmd(char const*, bool) + 24 bytes
  [15] libmwuix.dylib:doQuit(long) + 21 bytes
  [16] libmwuix.dylib:uix_DispatchOrProcess(_XEvent*, _XtAppStruct*, int, bool) + 457 bytes
  [17] libmwuix.dylib:ws_ProcessPendingEventsHelper(int, int, bool) + 593 bytes
  [18] libmwmcr.dylib:mcr::runtime::InterpreterThread::Impl::process_events(boost::shared_ptr<mcr::runtime::InterpreterThread::Impl> const&) + 465 bytes
  [19] libmwmcr.dylib:mcr::runtime::InterpreterThread::Impl::run(boost::shared_ptr<mcr::runtime::InterpreterThread::Impl> const&, mcr::runtime::InterpreterThread::Impl::init_context*) + 386 bytes
  [20] libmwmcr.dylib:run_init_and_handle_events(void*) + 60 bytes
  [21] MATLAB:start + 6315 bytes
  [22] MATLAB:start + 1761 bytes
  [23] libmwmcr.dylib:runMcrMain(void*) + 28 bytes
  [24] libSystem.B.dylib:_pthread_start~ + 316 bytes
  [25] libSystem.B.dylib:thread_start~ + 13 bytes
Why does this happen?
 

Best Answer

  • This is a known issue with MATLAB releases prior to R20010a for Mac OS platforms when forcing MATLAB to close while it is starting up.  For latest information please refer to the following bug report:
    For additional help, please contact the MathWorks Technical Support