How I Fixed my "DYLD shared region unnest for map"

Submitted by maz on Wed, 03/24/2010 - 14:26

Countless people have had this kind of thing appear in their dmesg output:

9/15/09 9:15:45 AMkernelSafari (map: 0x103f070c) triggered DYLD shared region unnest for map: 0x103f070c, region 0x7fff82c00000->0x7fff82e00000. While not abnormal for debuggers, this increases system memory footprint until the target exits.

System Events (map: 0x7697ae4) triggered DYLD shared region unnest for map: 0x7697ae4, region 0x7fff85e00000->0x7fff86000000. While not abnormal for debuggers, this increases system memory footprint until the target exits.

27/02/2010 14:28:11kernelProblem Reporter (map: 0x550de18) triggered DYLD shared region unnest for map: 0x550de18, region 0x7fff83600000->0x7fff83800000. While not abnormal for debuggers, this increases system memory footprint until the target exits.

I fixed mine by doing the following:

  • uninstalling MacFUSE
  • uninstalling SIMBL
  • going through /Library and deleting any leftover SIMBL or MacFUSE files (and removing the MacFUSE.prefPane too)
  • safe reboot (press and hold the shift key)
  • unloading all vmware and parallels modules listed in kextstat
  • deleting ConnectUSB.kext, Pvsnet.kext, hypervisor.kext, vmmain.kext
  • deleting /Library/Application Support/VMware Fusion
  • getting rid of Parallels and VMware applications (I used VirtualBox now)
  • rebooting

Happy Mac.

Tag:

Category: