Showing posts with label corrupt. Show all posts
Showing posts with label corrupt. Show all posts

Wednesday, June 26, 2013

Corrupted Preferences in Bridge? Try this and let me know if it works!

If you find your cache has become corrupted or otherwise unresponsive or damaged, Adobe's fix is pretty straightforward: go to Preferences and simply purge the cache.  (Of course, you'll have to reindex all your folders/filers.)

But if you find your Preferences themselves have become corrupted, it's a bit more challenging to find a solution to "reset" your preferences to the factory defaults. Here's what you do:
  1. Quite Bridge 
  2. Relaunch the program
  3. Immediately hold down Control-Alt-Shift (PC) or
  4. Command-Option-Shift (note if this doesn't work and for older versions of the Mac OS
I have to say, though, this did NOT work for me -- I suspect I would have to reinstall Bridge at some point. But that would mean a total reindex of our image library. I think not.

I'd be curious to know if this works for anyone else.

Tuesday, January 17, 2012

A window into Bridge's limits - or the corrupt cache issue, again

Well, it happened again: the dreaded “Bridge has a problem reading the cache. Purge the central cache.”


This has now happened twice on the G5 tower (my primary benchmark machine). Both times the cache had reached nearly identical size: 44gb, 364k+ items. the first time and 43gb, 352k+ items the second time.

Although a pattern seems to be emerging, it should be noted that the third time this happened was on my Macbook Pro and the size was somewhat smaller: 40gb, 298k+ items.

While we can't determine what this means with any degree of certainty, it just might indicate what the top end limits are in using Bridge.

Still. . . it pays to watch your cache levels carefully and optimize as needed (command/control + K in Bridge preferences)