Ask Different is a question and answer site for power users of Apple hardware and software. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Not sure if this is the right place for this, but my mac (mountain lion) has recently started crashing suddenly. Below is the error I get on restarting. Am I correct in assuming the issue is vim?

Interval Since Last Panic Report:  82178 sec
Panics Since Last Report:          1
Anonymous UUID:                    51D4695E-EFBC-5BD6-1E5B-B3EF5F297FDA

Tue Apr 23 11:55:08 2013
panic(cpu 4 caller 0xffffff8005b1fdca): "negative open count (c, 4, 0)"@/SourceCache/xnu/xnu-2050.18.24/bsd/miscfs/specfs/spec_vnops.c:1813
Backtrace (CPU 4), Frame : Return Address
0xffffff801289bc20 : 0xffffff8005a1d626 
0xffffff801289bc90 : 0xffffff8005b1fdca 
0xffffff801289bcd0 : 0xffffff8005b24c56 
0xffffff801289bd20 : 0xffffff8005b11c96 
0xffffff801289bd60 : 0xffffff8005af18a1 
0xffffff801289bdb0 : 0xffffff8005af1021 
0xffffff801289bdf0 : 0xffffff8005af1bea 
0xffffff801289be20 : 0xffffff8005b11fef 
0xffffff801289be50 : 0xffffff8005d56aed 
0xffffff801289bec0 : 0xffffff8005a39cc9 
0xffffff801289bef0 : 0xffffff8005a3c7c8 
0xffffff801289bf20 : 0xffffff8005a3c63e 
0xffffff801289bf50 : 0xffffff8005a1b70d 
0xffffff801289bf90 : 0xffffff8005ab8163 
0xffffff801289bfb0 : 0xffffff8005ace4bc 

BSD process name corresponding to current thread: Vim

Mac OS version:

Kernel version:
Darwin Kernel Version 12.2.0: Sat Aug 25 00:48:52 PDT 2012; root:xnu-2050.18.24~1/RELEASE_X86_64
Kernel UUID: 69A5853F-375A-3EF4-9247-478FD0247333
Kernel slide:     0x0000000005800000
Kernel text base: 0xffffff8005a00000
System model name: MacBookPro8,2 (Mac-94245A3940C91C80)

System uptime in nanoseconds: 71693486079601
last loaded kext at 64549837558237:   235.4 (addr 0xffffff7f87dd3000, size 12288)
last unloaded kext at 65047858804142:  4.1.22 (addr 0xffffff7f87dce000, size 12288)
loaded kexts:
org.virtualbox.kext.VBoxNetAdp  4.0.8
org.virtualbox.kext.VBoxNetFlt  4.0.8
org.virtualbox.kext.VBoxUSB 4.0.8
org.virtualbox.kext.VBoxDrv 4.0.8 1.8  1.9.5d0    4.0.9f33  1.60    3.0   100.12.69    122    3.5.10  1.0.0d1   8.0.0   1.0.33  4.0.9f33   2.3.1f2    3.0.2d6   2.3.1f2   8.0.0   1.6.0  1.0.0    2.0.2d0    3.2.11   7.0.0 3.2.11    1.0.0   1.0.0    8.0.0  235.4 235.4  320.15 1.0.0d1 1.0.0d1 34  3.5.1 404  2.2.2    5.2.5  1.2.2    3.2.5b3   602.15.22    4.9.6  2.4.1   5.4.0  1.6.1   161.0.0   1.6   1.5  1.7    1.9    1.6  1.6 196.0.0   4.0.39   2   196.0.0  10.0.6 1.0   86.0.3 4.0.9f33 2.3.1f2   1.8.9fc10    1.6    2.2.5 19.0.26   1.0.10d0   1.0.4   4.0.9f33   3.2.11   2.3.5   3.1.4d2 1.0.0 5.2.0d16    8.0.0   8.0.0 2.3.1f2    2.3.5 2.3.1f2  1.0.10d0    1.8.5    1.8.5 1.2.5 235.7  5.2.5   5.2.5  5.2.5  3.5.1   1.7  1.7.1   1.7.1   2.5.0   3.5.1    1.6.0 2.1.1 5.2.5 1.0.2b1   500.15  3.0    4.5.5    2.2.1 5.4.0    1.6.1 1.8.0   1.1  220   1.0.0d1  7 344 1.8  28.21  1.6 2.7.2    1.4    1.0
Model: MacBookPro8,2, BootROM MBP81.0047.B27, 4 processors, Intel Core i7, 2 GHz, 8 GB, SMC 1.69f3
Graphics: Intel HD Graphics 3000, Intel HD Graphics 3000, Built-In, 512 MB
Graphics: AMD Radeon HD 6490M, AMD Radeon HD 6490M, PCIe, 256 MB
Memory Module: BANK 0/DIMM0, 4 GB, DDR3, 1333 MHz, 0x80CE, 0x4D34373142353237334448302D4348392020
Memory Module: BANK 1/DIMM0, 4 GB, DDR3, 1333 MHz, 0x80CE, 0x4D34373142353237334448302D4348392020
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0xD6), Broadcom BCM43xx 1.0 (
Bluetooth: Version 4.0.9f33 10885, 2 service, 11 devices, 1 incoming serial ports
Network Service: AirPort, AirPort, en1
Serial ATA Device: Hitachi HTS725050A9A362, 500.11 GB
Serial ATA Device: MATSHITADVD-R   UJ-8A8
USB Device: FaceTime HD Camera (Built-in), apple_vendor_id, 0x8509, 0xfa200000 / 3
USB Device: hub_device, 0x0424  (SMSC), 0x2513, 0xfa100000 / 2
USB Device: Apple Internal Keyboard / Trackpad, apple_vendor_id, 0x0245, 0xfa120000 / 5
USB Device: BRCM2070 Hub, 0x0a5c  (Broadcom Corp.), 0x4500, 0xfa110000 / 4
USB Device: Bluetooth USB Host Controller, apple_vendor_id, 0x821a, 0xfa113000 / 8
USB Device: hub_device, 0x0424  (SMSC), 0x2513, 0xfd100000 / 2
USB Device: IR Receiver, apple_vendor_id, 0x8242, 0xfd110000 / 3
share|improve this question

migrated from Apr 24 '13 at 0:15

This question came from our site for professional and enthusiast programmers.

Nope, I use MacVIM all the time. Your issue is somewhere else. – Richard Brown Apr 23 '13 at 19:06
Vim is very stable here as well. If you are moderately certain it is a Vim issue, the vim-mac mailing list is a more appropriate place. – romainl Apr 23 '13 at 19:21
I agree I've been using vim for 8 years and never had problems. What to make of the "BSD process name corresponding to current thread: Vim" then? – pixelearth Apr 23 '13 at 19:25
@pixelearth Seems many have had this issue when using tmux. If you're using that, see if you can repeat the problem without it. – Joachim Isaksson Apr 23 '13 at 20:45
You know I too have the same problem suddenly cropping up. Yesterday, My Mac crashed as I was in a MacVIM Diff session. Then, today it happened again. Of course, I use MacVIM quite a bit in my job, so it may simply be coincidence that it was active when it happened. Apparently, there is some issue with MacVIM causing panics, and this is the second time I've seen tmux mentioned. – David W. Sep 17 '13 at 19:03

No the issue is probably not vim.

The crash report indicate the OS X kernel (xnu) crashed when vim was the current active process, but it's not necessarily vim that made the system crash. Actually vim is quite stable and run in user-space, so it's very unlikely that it made your system crash.

Note: By active, I do not mean front-most. For the multi-tasking to work, the kernel gives CPU time to all processes alternatively, switching fast enough to give the impression that all of the processes run “at the same time”. At the time of your crash, vim was the current process with CPU time.

share|improve this answer
How would I go about finding out what the issue is? It happens about once a week or so, always with VIM as the current process... – pixelearth Apr 24 '13 at 8:18
There are many possible causes for a kernel panic, most of them being a hardware (often memory) failure, or bogus kernel extensions. I would first recommend running the Apple Hardware Test (keep D down at boot to launch), perform Disk Checks and repairing permissions. If panics persist, try the links listed here: – Frizlab Apr 24 '13 at 11:57

This seems to be an issue that is covered under Apple TS4088 regarding spontaneous crashes, especially on mid-2010 MBPs. Worth investigating.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

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