MATLAB Answers

Why am I unable to start or install MATLAB on my Mac Pro (2013 or newer) with two Thunderbolt displays?

8 views (last 30 days)
If I connect two Thunderbolt displays to my new Mac Pro I am not able to run or install MATLAB. Is there any workaround?
These are the errors from Console and Crash logs:
A fatal error has been detected by the Java Runtime Environment:
# SIGSEGV (0xb) at pc=0x000000010ef43400, pid=13024, tid=5891
# JRE version: 7.0_11-b21
# Java VM: Java HotSpot™ 64-Bit Server VM (23.6-b04 mixed mode bsd-amd64 compressed oops)
# Problematic frame:
# C [libinstutil.dylib+0x9f400] l_getid_type+0xded
Java quit unexpectedly
Click Reopen to open the application again. This report will be sent to Apple automatically.

Accepted Answer

MathWorks Support Team
MathWorks Support Team on 20 Dec 2018
Edited: MathWorks Support Team on 20 Dec 2018
Background information
MathWorks is aware of a bug in MATLAB R2014a, R2014b, and R2015a related to MATLAB's licensing components which can affect the Mac Pro (2013+). This issue has been reported to the vendor (Flexera Software) responsible for MATLAB's licensing components. Many hardware configurations are affected, but a Mac Pro (2013) with two Thunderbolt Displays connected is particularly susceptible to this bug.
The bug will manifest itself on any hardware configuration where "ifconfig" reports more than ten "en" (Ethernet) interfaces. Since Thunderbolt Displays contain multiple network interfaces, connecting more than two of them to a Mac Pro (2013) will cause the Ethernet interface count to rise above ten. The Mac Pro (2013+) has nine built-in Ethernet interfaces, and Thunderbolt Displays contain an additional Ethernet interface which therefore increases the total Ethernet network interface count by one when a Thunderbolt display is connected.
To confirm whether a Mac is susceptible to this bug, launch the Terminal application and enter "ifconfig" at the prompt. A series of network interfaces will be listed. If the number of entries starting with "en" is greater than ten, then the Mac is susceptible.
This bug was resolved in MATLAB R2015b.
Workaround 1: Update to R2015b or later (Recommended)
This bug was fixed in MATLAB R2015b. The simplest way to resolve this issue is to update to R2015b or later.
*Workaround 2: Disconnect Extra Displays *
Disconnect devices from your Mac which add additional Ethernet network interfaces to reduce the total Ethernet interface count to ten or less. If you have multiple Thunderbolt Displays, disconnecting all but one of them is the quickest way to bring the count back down to ten.
When applying this workaround, devices disconnected cannot be reconnected while MATLAB is running. Doing so can cause the error to occur.
Workaround 3: Disable Thunderbolt Networking (Advanced Users)
NOTE: If you are not familiar with Terminal, please consult your IT department or use the recommended workaround listed above.
As an alternative workaround, you may run a command listed below, which will reduce the number of Ethernet interfaces until the next reboot by disabling IP-over-Thunderbolt functionality which most users do not need.
This will not unload your Ethernet or Wi-Fi interfaces, even those on your Thunderbolt Displays. This does not impact any other functionality of Thunderbolt. If you need to use these interfaces after unloading them, this is possible with another terminal command, or you can simply restart your Mac.
These devices must remain unloaded during your MATLAB session. If you decide to reload them, your MATLAB session may crash.
To unload the IP-over-Thunderbolt network interface, run the following command in Terminal (this command must be run each time your Mac restarts):
sudo kextunload -v /System/Library/Extensions/AppleThunderboltIP.kext
If you need to reload them (without restarting your Mac) you can run the following command in Terminal:
sudo kextload -v /System/Library/Extensions/AppleThunderboltIP.kext


Show 7 older comments
Jonathan on 16 Jul 2015
I made an little Automator application that does this on command, in case anybody is interested. You can get it at
In case you're worried, you should be able to open the application in Automator and confirm that it's not doing anything malevolent.

Sign in to comment.

More Answers (3)

Min H. Kim
Min H. Kim on 17 Oct 2014
I'm the one who addressed this issue to Mathworks about seven months ago. I'm currently using Matlab on a virtual machine instead of using the native workstation, Mac Pro w/ two thunderbolt displays. I expected a bug fix in this new version of Matlab 2014b and was disappointed in customer service, finding that the critical bug (addressed in seven month ago) remains in this latest update. Mathworks must publically and clearly announce that "Their latest product of Matlab cannot be run properly on a high-end configuration of Macintosh computers" in advertisements and product specifications. It is a serious liability issue to customers, who purchased this Matlab product of Mac without knowing this fact! Mathworks must realize that the importance of this bug fix and their liability to customers. Either Mathworks or the licensing product vendor (Flexera) must fix this faulty product at least by providing a bug patch as soon as possible.


Show 2 older comments
Andrew Roberts
Andrew Roberts on 31 Oct 2014
I experienced a similar "it's not our problem" response from Mathworks as detailed above. I have $10,000 worth of new computing equipment sitting on my desk that cannot run the latest version of MATLAB without disconnecting all but one screen, or running the command: sudo kextunload /System/Library/Extensions/AppleThunderboltIP.kext As detailed above. However, I agree about the customer service. I work on some of the fastest supercomputers in the world, and find the response of Mathworks strange. I purchased a Mac Pro with multiple screens because the hardware happens to be one of the best desktops around for scientific post-processing.
Gideon simpson
Gideon simpson on 4 Mar 2015
Mathworks really needs to step up on this kind of thing. Python just keeps getting better and better, and these kinds of issues are typically resolved quickly by the open source community. If Mathworks expects us to keep forking over significant amounts of money, that had better provide us with something that the open source community can't.
Shawn Lyons
Shawn Lyons on 1 Apr 2015
@Gideon Simpson
A fix for this issue is in the works for an upcoming release, likely version R2015b.
MathWorks Support

Sign in to comment.

Min H. Kim
Min H. Kim on 26 Mar 2015
Well... Here is an adhoc solution to make your launching simpler on your Mac. I wrote a simple bash script to launch Matlab 2015a in your command-line window on a Macro with two thunderbolt displays. Just type this in your command-line window as follows:
I'm using this on my computer, and it seems to work smoothly.
One thing tedious... You have to type your sudo password in your command-line window before launching Matlab. Just download, uncompress and copy this script where your path is set on your computer. I hope this script helps other people in our science and engineering community. - Min


Sign in to comment.

Joseph MacGregor
Joseph MacGregor on 16 Mar 2015
I am disappointed to report that this issue persists in R2015a. The solution still works, thankfully, but it doesn't speak well to the ability of Mathworks and Flexera to work together to fix identified problems in a timely manner. Step it up, guys.


Shawn Lyons
Shawn Lyons on 1 Apr 2015
@Joseph MacGregor
A fix for this issue is in the works for an upcoming release, likely version R2015b.
MathWorks Support
Jonathan on 6 Apr 2015
What's the point of bi-yearly updates if a bug of this significance and magnitude can't be addressed by the next update? You guys are putting out two updates a year but only doing work worthy of one every two years, at best...

Sign in to comment.


No tags entered yet.

Community Treasure Hunt

Find the treasures in MATLAB Central and discover how the community can help you!

Start Hunting!