Andy, since you do have the Java Update 10.5, this tells me that downgrading to 10.5_30 will not help me. I will try downloading an older version of Java 10.5.

Vy T.U. Dinh
Research Assistant, Neurological Sciences
Rush University Medical Center
Phone: (312) 563-3853
Fax: (312) 563-4660
Email: [log in to unmask]
From: Vy Dinh
Sent: Thursday, July 07, 2011 1:28 PM
To: Andrew Murrin; [log in to unmask]
Subject: RE: SPM/MATLAB Crashing

Hi Andy,

I'm pretty much in the same boat as you at this moment except that I upgraded to 10.6.0_24 on OS X 10.6 (Snow Leopard). What version of Matlab do you have? It appears that my Matlab versions  (2007a & 2008a/b) are incompatible with this new upgrade. I wonder if anyone with a Matlab version 2009 or later have the same problems?  I've tried downgrading to Java 1.5 using the instructions http://chxor.chxo.com/post/183013153/installing-java-1-5-on-snow-leopard but it appears that Matlab is still calling up the latest Java upgrade (type version -java in Matlab). If anyone has any luck following these instructions (http://www.mathworks.com/support/solutions/en/data/1-1812J/) please share! Thanks.


Vy T.U. Dinh
Research Assistant, Neurological Sciences
Rush University Medical Center
Phone: (312) 563-3853
Fax: (312) 563-4660
Email: [log in to unmask]
From: SPM (Statistical Parametric Mapping) [[log in to unmask]] on behalf of Andrew Murrin [[log in to unmask]]
Sent: Thursday, July 07, 2011 12:54 PM
To: [log in to unmask]
Subject: [SPM] SPM/MATLAB Crashing

SPM Community:
    I am using SPM5 on a Mac with OS X 10.5.8, and everything was working fine up until the last set of software updates – Java Update 10.5.0_30, as well as the Cumulative Security Update for Macs.  I am able to load MATLAB without any issues, but after typing “spm” (“figure” is another command that causes this, so it is not *entirely* SPM-related) at the command prompt, the initial button selection window for SPM (where you can select “fMRI”, “EEG”, etc.) appears and then MATLAB crashes.  From general online searches, it appears that the latest Java update is causing the issues.  I am just wondering if anyone else is experiencing this, and knows any solutions.  Thanks!

- Andy