Oddly, If I drag the Bridge folder out of the Application Support folder and start it again, it works fine. if I modify anything (to rebuild all the missing folders at that location) and quit and start up again, the crash happens again.

I don't know if it is just me, my configuration, applications that I use, some new OSX Mountain Lion "security feature"... But .zip files are all around and Bridge keeps crashing every time, this is a big issue for me.

I don't have a crash with zip or doc files, and I seemed to have fixed my other problem by enlarging the icons a little bit and then restarting...at least it hasn't happened again (so far) after doing that.

Same here. I wonder if it has anything to do with file type association. If you check, (under Preferences) neither zip files nor word docs are on the list. And it appears there is no way to add a new file type, so I can at least test my theory.

Same problem here, though no relation with .zip archives, as far as I can tell. Apparently Bridge wants to write some prefs to your hard disk. I solved it by changing permissions to my hard disk. Set group everyone to read and write, than start Bridge. It should start up fine now. Once it is started up, you can change your permissions back to their defaults. This did the trick for me.

In Bridge and Photoshop forum lots of problems with Mt. Lion and Adobe products. Are you people getting any help from Apple? Since the OS update created a raft of problems they should be the primary avenue for fixes.

g4zilla, I've changed the Open With option as you suggested, and so far, so good, the folders that seemed to be crashing Bridge are not anymore. What I can't quite work out is that I've had Mt Lion installed for the last couple of weeks, and apart for once where it crashed for a little while, it was working fine again after reboot. This morning though, it suddenly started crashing left right and centre trying to access folders I previously didn't have any issue accessing.

vaughaag2004, I've just done what you suggested and switched back the Open With to the default expander for zip files, and so far, Bridge hasn't crashed, even when jumping from one folder containing a zip file to another. Will keep it running today and see whether this continues to work.

I don't know whether this is just a fit of my imagination, but Bridge also seems to be faster. Fingers crossed...

@vaughaag2004: I gave it a go, and then tested by changing the default "Open With..." to Archive Utility on one file only. (The folder contained other zip files, but they were connected to Stuffit Expander) Bridge launched and loaded OK.

So, I enacted the system-wide change to make all zip files open with Archive Utility, and then launched Bridge again. It worked without crashing. Though I had zero crashes by making the previous change I suggested a few posts above, I'm going to leave things with this new setup and see how it goes.

Since I had it working on the iMac, I decided to upgrade the MBP today. I carried out a clean install, then installed CS5.5 and Bridge kept crashing. I did the fix I listed above and its working fine now.

There has to be something within ML that stops Adobe altering/creating the folder permissions.

Since this turned out to be, not surprisingly, a permissions problems, I wonder whether Mac users have forgotten or neglected the time-proven advice to REPAIR PERMISSIONS with Apple's Disk Utility before AND after installing any application, update or upgrade, as well as before AND after every install, update or upgrade of the OS. Without exception.

Mac users have forgotten or neglected the time-proven advice to REPAIR PERMISSIONS with Apple's Disk Utility before AND after installing any application, update or upgrade, as well as before AND after every install, update or upgrade of the OS. Without exception.

Repair Permissions with Apple's Disk Utility, Mac Users,

immediately before and immediately after an install, re-install, update or upgrade.

Possibly for some. But considering the same problem existed after a 100% clean OS install and for those who have bought new devices with ML preinstalled then installed CS5.5, I think there is a bit more of an underlying problem.

After a clean install of the OS, I would definitely and without exception run Disk Utility and Repair Permissions. Always.

When buying a new machine the first two things I always do are (1) wipe the drive clean and write it to zeros, and (2) Repair Permissions right after installing a fresh OS on it as well as after any immediate update of said OS. If the update does not happen immediately after the new installation of the OS, I would definitely Repair Permissions again before the update too, then immediately afterwards.

On the other hand, if by "ML" you are referencing Mountain Poop, then all bets are off, of course.

Maybe Apple will get it that OS right by version 10.8.6. They never seem to get a new OS right before the dot-six release, that's why Lion never had a chance to mature.

(I thought I had already posted this message earlier, but inexplicably, it's not here. I hope it was not removed because of my deservedly derogatory reference to the latest Apple Mac OS.)

@station_two - I can appreciate where your coming from but every OS from Windows/OSX through to the most stable of UNIX systems have 100's of faults when they are released. Users reporting these faults form a key part of making the system better and is an essential part of the evolution process, updates, service packs and new releases etc.

The problem comes where the programmers and/or software houses do not reply to users offering support or acknowledge that there is a problem in the first place, something that happens all too often.

In my opinion there are plenty of places on the net to slate specific OS's, support forums are not necessarily the right place.