In trying to track down a fix for a problem I started experiencing after upgrading my MacBook Pro to Leopard, I came across something that might end up being the solution not only to own my issue (see
http://macosx.com/forums/mac-os-x-s...rmanent-wireless-connection-under-leopar.html), but also to other mysterious and hard-to-reproduce problems that have been cropping up for some of us after Leopard upgrades or installations.
Here's how to tell if you have problems that might be solved by this procedure, and how to apply the fix:
- Open up the file /var/log/system.log
- See if you have lines inside the log that look similar to this one:
- If so, and if the message involves com.apple.dyld, open a Terminal session and issue the following command:
This fixes what appears to be a case of dyld cache corruption that has been seen to occur for at least some people after the first software upgrade that follows a Leopard install. This corruption causes dyld to periodically fail and have to be restarted, and this, in turn, can affect lots of different programs on your system.
Of course, this fix will not correct each and every problem that people might be having under Leopard, but based on some of the discussions I have found on the net, it seems like it does solve a class of difficult-to-diagnose problems that a number of folks have been experiencing:
Good luck with this!
http://macosx.com/forums/mac-os-x-s...rmanent-wireless-connection-under-leopar.html), but also to other mysterious and hard-to-reproduce problems that have been cropping up for some of us after Leopard upgrades or installations.
Here's how to tell if you have problems that might be solved by this procedure, and how to apply the fix:
- Open up the file /var/log/system.log
- See if you have lines inside the log that look similar to this one:
Nov 11 10:03:51 home com.apple.launchd[1] (com.apple.dyld): Throttling respawn: Will start in 6 seconds
- If so, and if the message involves com.apple.dyld, open a Terminal session and issue the following command:
sudo update_prebinding -force -root /
- Then, reboot.This fixes what appears to be a case of dyld cache corruption that has been seen to occur for at least some people after the first software upgrade that follows a Leopard install. This corruption causes dyld to periodically fail and have to be restarted, and this, in turn, can affect lots of different programs on your system.
Of course, this fix will not correct each and every problem that people might be having under Leopard, but based on some of the discussions I have found on the net, it seems like it does solve a class of difficult-to-diagnose problems that a number of folks have been experiencing:
http://blog.eleventyten.com/2007/10...ld-throttling-respawn-will-start-in-n-seconds
http://forums.macrumors.com/showthread.php?t=376542
http://forums.macrumors.com/showthread.php?t=376542
Good luck with this!
.