Skip to main content
Participant
January 21, 2024
Question

Bridge 14.0.1 Crashing Constantly

  • January 21, 2024
  • 1 reply
  • 174 views

Adobe Bridge keeps crashing randomly. Whenever I'm working through CR3 files it crashes and gives me a crash report. It crashes when I'm working through CR2s also but I don't get a crash report for that the app just closes. 

It also crashes a lot whenever I'm saving files from camera raw, regardless of if I'm saving CR2 or CR3 files. I've already purged the cache so I'm not sure what the problem is.

This topic has been closed for replies.

1 reply

Inspiring
January 21, 2024

I ran into the same problem a couple of days ago and, after extensive bug-shooting, I am fairly confident that, in my case, this was due to the presence of a Script which interferes with Br 14.


There is a Script called Custom Metadata Panel which I downloaded from ACC and tried many years ago. 
It caused crashes and instability; and was not useful to me anyway; so I trashed it — or thought that I had. 
Apparently I had not done this thoroughly enough because that Script reappeared when I re-edited my older NEFs.
I could not get rid of it but found an updated plug-in version on ACC and installed it; then trashed it (its only usable under Rosetta); and that finally seems to have cleared the Script out of my computer.
The result is that I am no longer getting the Bridge PR freeze-ups which were plaguing me previously.
 
I am updating older NEFs to the newest build of ACR  and acknowledge that these are very large folders which may contain over 5000 RAW NEFs; and that I am working on folders that are located on a HD across a WiFi connection; but there was definitely some malfunctioning with Br 14.
(This is on Mac OS 14.2.1 Sonoma).

 

Since I removed all traces of "Custom Metadata Panel", I have not had a single freeze or crash of Br 14 for over two days.
 
Others who experience slow preview-building and frequent crashes and freezes might want to check their Scripts to see if the Custom Metadata Panel (or any other add-on Script) is present; and see if disabling those Scripts cures their problems.