Bug fixed in 10.1.0 (see answer for details)

Since update to Mathematica has a high CPU usage even when no evaluation is running (even for empty notebook opened). I am running OS X Yosemite 10.10.3 on the following configuration:

  • Model Name: MacBook Pro
  • Model Identifier: MacBookPro5,5
  • Processor Name: Intel Core 2 Duo
  • Processor Speed: 2,26 GHz
  • Number of Processors: 1
  • Total Number of Cores: 2
  • L2 Cache: 3 MB
  • Memory: 8 GB
  • Bus Speed: 1,07 GHz
  • Boot ROM Version: MBP55.00AC.B03
  • SMC Version (system): 1.47f2

In1:= SystemInformation["Kernel", "ReleaseID"]
Out1= " (5292907, 2015032401)"

My colleague reports the same on similar machine. Is this a bug?

Activity Monitor screenshot. There is a single empty notebook opened in Mathmatica.

  • 2
    $\begingroup$ same here. Mathematica v10.1 on Mac OS X 10.10.3. $\endgroup$ – sunt05 Apr 22 '15 at 19:33
  • 9
    $\begingroup$ I can confirm that this is a bug in Mathematica 10.1.0 on OSX, and appears to mostly happen on older MacBookPro machines (with Core 2 Duo processors). We do so far not have a workaround, but are actively working on a fix. $\endgroup$ – Stefan R Apr 22 '15 at 19:48
  • 1
    $\begingroup$ I just want to chime in with a confirmation. I've been having this issue since was released. I've emailed Wolfram and gotten no response. But for now i'm solving my problem by simply redownloading 10.0.2 and getting back to work. $\endgroup$ – BlBl Apr 24 '15 at 20:07
  • 1
    $\begingroup$ @SquareOne Yes we have a fix. Please contact support@wolfram.com for details. $\endgroup$ – Stefan R May 1 '15 at 22:26
  • 1
    $\begingroup$ @StefanR Good news !! Maybe you can post this important information as an answer to this post, as many users are waiting for it. BTW what kind of fix is it ? (a new version to download ?) $\endgroup$ – SquareOne May 1 '15 at 23:59

This is a bug in Mathematica 10.1.0 on OSX, and seems to primarily, but not exclusively, affect older MacBookPro machines with Core 2 Duo processors.

We have identified the cause and devised a fix. Unfortunately, the fix is not simple, and requires replacement of a few key components. We have created a patched version of Mathematica 10.1.0 which is completely identical except for the aforementioned components.

For now, we are only handing this patched build out to customers that have run into this issue. So if you are affected, please contact support@wolfram.com for further instructions.

Update The Mathematica 10.1.0 for OSX installer in the User Portal is being replaced with the installer for the patched version in the next couple of days. The way to tell the difference is that the DMG disk image for the patched version has the MD5 checksum c347b7e1f79dad90a98859037cac1ccf.

  • 1
    $\begingroup$ I emailed support and got the patched version. Indeed it fixed the problem. $\endgroup$ – Mark Adler May 8 '15 at 22:58
  • 1
    $\begingroup$ Why not give it a new version number? This seems bound to confuse people (like I was). $\endgroup$ – Pontus Granström May 20 '15 at 9:48
  • $\begingroup$ @PontusGranström To make sure we got the fix out as soon as possible. Changing the version number can subtly affect a surprising number of things, both in Mathematica and in the build system we use, and can introduce bugs. $\endgroup$ – Stefan R May 20 '15 at 18:55

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.