Strong opinions, weakly held

Snow Leopard: dyld issue

Since updating my Mac running Snow Leopard to 10.6.1, I’m seeing the following message in the Terminal at least once after running every command:

dyld: shared cached file was build against a different 
libSystem.dylib, ignoring cache

Someone said online that you can clear the cache using the following command:

sudo update_dyld_shared_cache -force

That returned the error:

update_dyld_shared_cache failed: vm address 0xFEEDFACE not found 
in /System/Library/Frameworks/Accelerate.framework/Versions/A/

I was hoping to post a solution to the problem for other people, but I haven’t solved it yet! So if you have any ideas, please post a comment.

Update: Looks like the library that’s preventing me from updating the dyld cache is in the hardware acceleration framework. Here’s one proposed solution, which involves moving the offending framework, running update_dyld_shared_cache and then moving the framework back. I’m not entirely comfortable with that.


  1. The clearing of the cache worked for me. Thanks!

  2. Clearing cache worked out well. Thanks!

  3. sudo update_dyld_shared_cache -force

    Work for my … many thanks !!

  4. I’m having the same problem as you (and have been for some time now), in that “sudo update_dyld_shared_cache -force” (even after safe booting) doesn’t fix the problem. Most irritating.

  5. Under 10.6.2 Restarting the computer in Safe Boot mode deletes the dynamic-loader shared cache. If you suspect the shared cache is somehow corrupt, you can run: sudo update_dyld_shared_cache -verify

    which re-creates the cache and compares the result with your actual cache file. The launch time of Cocoa programs has been improved by caching some Objective-C runtime fix ups in the shared cache. Thus the Objective-C runtime has less work to do during launch. Be PATIENT it could take up to 4 to 6 minutes on some system


Leave a Reply

Your email address will not be published.


© 2024 rc3.org

Theme by Anders NorenUp ↑