Why does MATLAB 7.13 (R2011b) crash on a Mac while using the Variable Editor?

MATLAB 7.13 (R2011b) crashes when I modify an element of an array using the Variable Editor or resize the columns of the Variable Editor. This happens irrespective of whether the Variable Editor is docked or undocked. This did not occur prior to my recent upgrade to OS X 10.6.8 on the Mac.

MATLAB on certain ocassions crashes while in debug mode, as I step through the code line by line.

MATLAB crashes while scolling through the Workspace Window.

Answer 1

[MathWorks Support Team]

This bug has been fixed in MATLAB 8.0 (R2012b). For previous product releases, read below for any possible workarounds:

There is a bug in MATLAB 7.14 (R2012a) 64-bit and earlier releases (64-bit) in the way that MATLAB crashes while using Variable Editor or Workspace Window when running on Java Version 1.6.0_26 or 1.6.0_29 or 1.6.0_31 provided by Apple Inc. for Mac OS X. The cause of the crash has been identified to be within Java Just-In Time (JIT) Compiler.

For MATLAB 7.14 (R2012a), there is a patch available for download on MathWorks website in the form of a published Bug Report here (Bug ID#:749571)

https://www.mathworks.com/support/bugreports/749571

The Bug Report provides the patch files and instructions for installation of the patch.

Note: You will need to Log In using your MathWorks Account credentials in order to be able to view the bug report.

If the issue is not fixed by the patch, there is a possibility that the patch was installed incorrectly. To verify the installation execute the following two commands,

cd(matlabroot)
ls -ld java/jar/widgets.jar

In a correct installation, the file should be dated July 23, 2012.

For MATLAB 7.13 (R2011b) and earlier releases refer to the following instructions.

As a workaround, disable the Java JIT as follows, in exchange for a small compromise in performance:

1) Create a text file named "java.opts" in the $MATLABROOT/bin/$ARCH directory. $MATLABROOT is the MATLAB root directory and $ARCH is the system architecture, which can be found by typing the following at the MATLAB Command Prompt:

        >> matlabroot
        >> computer('arch')

If the user does not have write-access to $MATLABROOT/bin/$ARCH, or if a user-specific version is desired, create the "java.opts" file in the MATLAB startup directory. The MATLAB startup directory can be found by executing the following at the MATLAB Command Prompt (before any MATLAB code is executed):

        >> pwd

Note: java.opts files can reside in the folder from which you launch MATLAB or in the bin/$ARCH subfolder within the MATLAB root folder. A java.opts file in the latter location applies to all users, but individual users might not have permissions to modify a java.opts file there. If there is a java.opts file in both locations with settings that conflict, the setting in the java.opts file in the folder from which you launch MATLAB takes precedence. You might want to check both locations to see whether you have existing java.opts files and then decide which one to modify.

At the $MATLABROOT/bin/$ARCH or at the startup directory, create a text file named 'java.opts', if one is not there already, by typing the following:

        >> edit java.opts

2) In the MATLAB editor, enter the following lines and save "java.opts" :

              -Dapple.awt.graphics.UseQuartz=true 
              -Xint

The option -Dapple.awt.graphics.UseQuartz=true forces Java to use the Quartz rendering pipeline to improve rendering performance.

The option -Xint is used to turn off the Java Just-In-Time.

3) Exit and restart MATLAB, and check if the crash issue still occurs.

If this workaround does not work or creates additional issues, revert back to the previous state by deleting the "java.opts" file you created.

Note: Disabling Java JIT may affect MATLAB performance.