Kernel panic - mavericks, logic pro, totalspaces2

I recently started using Logic Pro X on my Mavericks system. I have been using totalspaces for years, love it. I’m getting random kernel panics in Logic and what seems to trigger it the most is when I use total spaces to go to the grid view and then switch desktops. It doesn’t happen all the time, but I’ve been able to replicate the panic several times that way.

Anyone have any idea what might be going on?

Latest Mavericks
Latest Logic Pro X
Latest stable totalspaces2

I also completely reinstalled a totally fresh Mavericks and don’t have anything else installed, only Apple stuff, Logic Pro and Totalspaces.

The kernel panic i get looks like this usually:

Anonymous UUID: C381AEE9-3917-B905-34E4-5E3A756B1365

Tue Oct 13 10:53:19 2015
panic(cpu 2 caller 0xffffff7f89bedf7c): “GPU Panic: [] 5 3 7f 0 0 0 0 3 : NVRM[0/1:0:0]: Read Error 0x00000100: CFG 0xffffffff 0xffffffff 0xffffffff, BAR0 0xd2000000 0xffffff81239f8000 0x0a5480a2, D0, P2/4\n”@/SourceCache/AppleGraphicsControl/AppleGraphicsControl-3.6.22/src/AppleMuxControl/kext/GPUPanic.cpp:127
Backtrace (CPU 2), Frame : Return Address
0xffffff8109fbaea0 : 0xffffff8007823139
0xffffff8109fbaf20 : 0xffffff7f89bedf7c
0xffffff8109fbaff0 : 0xffffff7f882c6f1b
0xffffff8109fbb0b0 : 0xffffff7f8839050a
0xffffff8109fbb0f0 : 0xffffff7f8839057a
0xffffff8109fbb160 : 0xffffff7f8860f056
0xffffff8109fbb290 : 0xffffff7f883b3ba9
0xffffff8109fbb2b0 : 0xffffff7f882cd96d
0xffffff8109fbb360 : 0xffffff7f882cb478
0xffffff8109fbb560 : 0xffffff7f882ccdc7
0xffffff8109fbb630 : 0xffffff7f891fd3df
0xffffff8109fbb700 : 0xffffff7f892277b3
0xffffff8109fbb780 : 0xffffff7f8920fae0
0xffffff8109fbb7e0 : 0xffffff7f892103da
0xffffff8109fbb830 : 0xffffff7f89210754
0xffffff8109fbb8a0 : 0xffffff7f89210fc8
0xffffff8109fbb8e0 : 0xffffff7f891ddfea
0xffffff8109fbba60 : 0xffffff7f8920d940
0xffffff8109fbbb20 : 0xffffff7f891dcad9
0xffffff8109fbbb70 : 0xffffff8007cd0826
0xffffff8109fbbb90 : 0xffffff8007cd1e21
0xffffff8109fbbbf0 : 0xffffff8007ccf88f
0xffffff8109fbbd40 : 0xffffff80078b6e18
0xffffff8109fbbe50 : 0xffffff8007826d81
0xffffff8109fbbe80 : 0xffffff8007813af5
0xffffff8109fbbef0 : 0xffffff800781e1d3
0xffffff8109fbbf70 : 0xffffff80078ca13d
0xffffff8109fbbfb0 : 0xffffff80078f4ca6
Kernel Extensions in backtrace:[32862231-50BC-3AF6-87A2-703321AE4F90]@0xffffff7f89bdf000->0xffffff7f89bf2fff

BSD process name corresponding to current thread: WindowServer

Mac OS version:

Kernel version:
Darwin Kernel Version 13.4.0: Wed Mar 18 16:20:14 PDT 2015; root:xnu-2422.115.14~1/RELEASE_X86_64
Kernel UUID: 8B1A8FD1-2344-36C0-A7F5-D9D485A995FA
Kernel slide: 0x0000000007600000
Kernel text base: 0xffffff8007800000
System model name: MacBookPro6,2 (Mac-F22586C8)

System uptime in nanoseconds: 32810781562371
last loaded kext at 413400145928: 2.0.3 (addr 0xffffff7f89cf7000, size 335872)
last unloaded kext at 306875468557: 1.9 (addr 0xffffff7f89cf7000, size 57344)
loaded kexts: 2.0.3 1.9.5d0 3.0 4.2.7f5 1.60 100.14.34 124 2.6.3f4 1.0.0d1 2.6.3f4 3.5.13 8.2.4 8.2.4 4.2.7f5 7.0.0 1.2.5 1.0.0 2.0.4d1 1 1.7.0 3.6.22 1.0.0 8.2.4 3.0.4d1 240.2 325.7 240.2 3.4.1 3.4.1 1.0.0d1 1.0.0d1 1.0.0d1 35 3.6.7 404 2.6.0 5.0.2 683.4.0 3.8.1b2 700.20.22 3.0.5 660.4.0 161.0.0 2.0 2.0 1.8 2.1 2.0 1.7 217.92.1 153 3 217.92.1 1.0 10.0.7 3.6.22 2.6.3f4 1.0.0 1.9.7fc2 1.14 91.3 4.2.7f5 8.2.4 8.2.4 4.2.7f5 1.0.12d1 2.2.6 2.6.3f4 2.6.3f4 1.0.12d1 1.0.4 3.6.22 1.0.0 5.7.1d6 2.4.1 2.4.1 3.1.8 240.10 660.4.0 3.6.7 3.6.0 2.5.1 4.2.6 650.4.0 656.4.1 3.6.7 1.7 1.7.1 1.7.1 2.6.1 3.6.7 4.5.5 660.4.2 1.0.3b4 1.0.1b5 640.36 3.2 2.6.5 686.4.1 2.0 2.0 2.0.0 1.1 278.11.2 1.0.0d1 7 2 373 1.9 23 28.30 2.0 2.9 1.4 1 1.0

The only thing that comes to mind is that the grid does make heavy use of the graphics card - it has to show replicas of each window you have, together with scaled desktop backgrounds and so on.

If logic pro is taxing the GPU also then probably this creates the conditions for this particular read error.

I have two suggestions:

  • In general preferences set the grid backgrounds to Lo res, or none.
  • Go to a terminal and issue the following command: defaults write com.binaryage.TotalSpaces2 lowerMemoryUsage -bool YES
    (here you are trading a little speed for less load on the GPU memory)

Let me know if this helps.

Interesting. I’m trying to figure out if my MBP has a faulty logic board (with the GPU). I found lots of people complaining about this on the net and apparently for a while there Apple was replacing Logic boards on my model year MBP, but they stopped doing it now, I guess I didn’t find out about it in time. The thing is, the problem has only come up with Logic Pro…and since I stopped using Totalspaces, also haven’t had the problem either.

So I don’t know if I still need to go to my Genius Appt to have my logic board checked, or if this kernel panic is to be expected, even from a perfectly healthy logic board and GPU. It sounds like you’re saying it could potentially happen even for perfectly healthy hardware. Usually kernel panics are from not so healthy hardware or drivers or conflicts between hardware of some kind. It could be that whatever you’re doing in Totalspaces is getting down and dirty with the hardware enough to push the machine into some kind of conflict over resources that would not normally happen… Or…it could be the hardware is dying and I need to beg Apple to fix it. Right now I’m trying to run without Totalspaces to see if I can get the failure to happen without Totalspaces… but so far, no luck. I can actually live without it and get used to Mission Control once and for all though I miss the grid overview already. But mainly I need to figure out whether the problem is software related or hardware related at the moment.


TotalSpaces uses high level APIs, it’s mostly Core Animation, and not anything deep in the GPU. But I have seen machines struggling because of the extra work the graphics system is doing, so that was the genesis of the lower memory setting (it actually just stops TS from caching the windows shown in the overview grid).

I have a feeling that kernel panics ought to be due to either a low level bug or a hardware problem - but as you rightly point out there could be a conflict of some sort that is only triggered by the resource contention.

It’s very hard indeed to find out if it’s hardware or software related unless you have a second machine of the exact same type to compare with.

But I think it would be worth trying TS with the lower memory setting turned on.