Bridge 6.1.1.10: Continuous crashing on Mac OS X 10.11.3 El Capitan

  • 3
  • Problem
  • Updated 2 years ago
  • Solved
  • (Edited)
Adobe Bridge CC 6.1.1.10 (latest Version) crashes at least once a day under Mac OS X 10.11.3 El Capitan. I am a photographer and work with a MacBook Pro 13" (mid 2012 model with Intel HD4000, 8GB RAM, 512GB SSD). Normally when I work with Bridge editing pictures and working with them in Adobe Camera Raw 9.4, I use the software more than 8 hours and in that time it will crash at least one (today three times).

External Display and harddisks are connected (via Displayport and USB 3.0). When I work without anything connected to the MacBook, Bridge seems stable. But that is not a solution.

I tried everything troubleshooting (uninstall, clean install Mac OS X, install Adobe CC again, change RAM, use other account, deleted user account fonts  and so on ... really everything).

I cannot see the reason why, console log says (only the important things here):

Crashed Thread:        0  Dispatch queue: com.apple.main-thread
Exception Type:        EXC_BAD_ACCESS (SIGSEGV)
Exception Codes:       KERN_INVALID_ADDRESS at 0x0000000000000020
Exception Note:        EXC_CORPSE_NOTIFY

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread0   libobjc.A.dylib               0x00007fff8225716f objc_release + 31
1   com.apple.CoreFoundation       0x00007fff83cc3102 _CFAutoreleasePoolPop + 50
2   com.apple.Foundation           0x00007fff8a62fcb6 -[NSAutoreleasePool drain] + 153
3   com.apple.AppKit               0x00007fff91d6209b -[NSApplication run] + 893
4   com.adobe.bridge6             0x000000010d14b387 0x10cab5000 + 6906759
5   com.adobe.bridge6             0x000000010d1443e9 0x10cab5000 + 6878185
6   com.adobe.bridge6             0x000000010d1444bc 0x10cab5000 + 6878396
7   com.adobe.bridge6             0x000000010d21b367 0x10cab5000 + 7758695
8   com.adobe.bridge6             0x000000010d21b994 0x10cab5000 + 7760276
9   com.adobe.bridge6             0x000000010cab7414 start + 52

It is not like I am loosing data, sometimes I have to start RAW to JPG conversion again and it gets on my nerves ...

Thanks in advance for every helpful hint!
Photo of jobumac

jobumac

  • 44 Posts
  • 1 Reply Like

Posted 3 years ago

  • 3
Photo of Chris Cox

Chris Cox

  • 20280 Posts
  • 815 Reply Likes
This problem is new in MacOS 10.11. The Bridge team has notified Apple and is waiting for a response/solution.
Photo of Paul Vlachos

Paul Vlachos

  • 2 Posts
  • 0 Reply Likes
What led me here is not continuous crashing but, out of the blue, inability for Bridge to start up. I just installed CC a week ago and it's all been working fine. No changes to my machine, but bridge suddenly won't start up. I have tried an awful lot of things, ranging from permissions changes to preference deletions to re-installations. Nothing.
Photo of jobumac

jobumac

  • 44 Posts
  • 1 Reply Like
Thank you. I had five crashes since I posted my problem. Should I send you the crash logs? Often a crash happens when I quit Bridge CC by the way.
Photo of Chris Cox

Chris Cox

  • 20280 Posts
  • 815 Reply Likes
Send the logs to Adobe and Apple.  This is a known issue, so we don't need any more posted here.
Photo of Anne Evans

Anne Evans

  • 3 Posts
  • 0 Reply Likes
I am having the same problem. I am a professional photographer / artist and rely on Bridge and Photoshop. This is doing my head in now! 

In Photoshop I can no longer save as a jpeg file either, which my website requires for upload. Not  happy bunny! 
Photo of Chris Cox

Chris Cox

  • 20280 Posts
  • 815 Reply Likes
Yes, sorry that this MacOS 10.11 bug is hurting your workflow.  Unfortunately the Bridge team can only wait for Apple to respond on this issue.

Why can't you save as JPEG in Photoshop?
Photo of Anne Evans

Anne Evans

  • 3 Posts
  • 0 Reply Likes
Thanks for the response. I do my first round of post production in Bridge.

The first issue is in Bridge if I double click to open an image from a file doesn't work, but that is less of a problem as I can go to File, open.

In Photoshop after post production work the option to save as jpg file has completely gone. I have tried it with various files and it's just not there.

I am using CS4. My original training was in a Photography BA honours degree course completed in 2012.
Photo of Chris Cox

Chris Cox

  • 20280 Posts
  • 815 Reply Likes
Sounds like you're in 16 bit/channel or 32 bit/channel - which JPEG doesn't support.
JPEG only supports 8 bit/channel images in Grayscale, RGB, or CMYK.
Photo of Anne Evans

Anne Evans

  • 3 Posts
  • 0 Reply Likes
Cheers for that Chris, I hadn't checked that.  Somehow the most recent upgrade had changed the default to open an image from raw into photoshop as a 16bit image. I hadn't changed it. I've gone in and altered the setting now to open as 8bit in photoshop and all is good. Save as 'jpg' is back. 
Photo of Ines Oehlmann

Ines Oehlmann

  • 1 Post
  • 0 Reply Likes
bridge is quitting on my and i do rely on it as well. the other day tech support helped me with troubleshooting and they said it won't quit again, well after couple days is quitting again, and i reached out to them today and they said the experts are only working monday - friday
Photo of jobumac

jobumac

  • 44 Posts
  • 1 Reply Like
Hello,

there is a new version of Adobe Bridge CC (version 6.2) - finally! Great news, but if you encounter still the same problem, I would like to share my last experiences with you:

Last week I tried out several things to narrow down the problem. First my setup: I use a MacBook Pro (mid 2012, i7 2,9 GHz, non-retina), 10.11.3 and the latest Adobe Photoshop CC 2015 and Adobe Bridge CC version plus an Indesign CS5 (version 7.0.4) and Bridge CS5 (which I do not use) installation. I installed 16 GB RAM and a Samsung 512 GB 850 Pro SSD, with TRIM enabled (via the trimforce command in Mac OS X 10.11, further information about TRIM in Mac OS X 10.11: How to Enable TRIM on Third Party SSDs in Mac OS X with trimforce).


My workflow:

My current jobs are on my MacBook, my archived jobs are on an external disk connected via USB 3.0. After every job I export the cache to the job folder and move it to my archive on the external disk.

 Attempt to find out more about the problem:

I gave the second 10.11.4 public beta a chance and installed it, wether to see if something will change. After I installed it, I had no crashes with Adobe Bridge CC - although without extensive testing. I also noticed, that the beta of 10.11.4 disabled TRIM on my system. Then I reverted with my time machine backup back to 10.11.3 and disabled TRIM via trimforce command (see the link above).

After that my system runs more stable. Apparently there is something wrong with the Mac OS X TRIM command in conjunction with the Samsung 850 PRO SSD.

During last week I also checked activity monitor in Mac OS X and noticed that two system processes connected with Bridge CC stopped working or stalled:

Adobe SwitchBoard and MRTagent (the MRTagent is installs with Java 6, which is needed for Adobe CS5).

I completely deleted Adobe SwitchBoard and also the MRTagent then. Both are not really needed and the apps are working fine until now (my experience).

How to remove Adobe SwitchBoard:

- kill the process in activity monitor

- check your login items for adobeswitchboard.plist and delete it

     ~/Library/LaunchAgents

     /Library/LaunchAgents

     /Library/LaunchDaemons    

     /Library/StartupItems

- delete ~/Library/Preferences/Adobe/SwitchBoard

- delete SwitchBoard within the Adobe Bridge CC app:

     - right click on the Adobe Bridge CC application > show package content and navigate to Contents/MacOS and delete SwitchBoard, after that navigate to Contents/Frameworks/ and delete SwitchBoardClient.bundle

How to remove MRTagent, please read this:

http://www.cnet.com/news/a-look-at-apples-flashback-removal-tool/

I learned that file names can differ to the above guidance. I deleted everything connected to MRT or MRTagent.

But please double check for yourself when removing system files.

Thanks Adobe for keeping Bridge alive again!

:)

Photo of sam ashley

sam ashley

  • 2 Posts
  • 0 Reply Likes
Is anyone at Adobe aware of how many people this is affecting? Is anyone working on a fix?
See here: https://forums.adobe.com/thread/2080582
Photo of Chris Cox

Chris Cox

  • 20280 Posts
  • 815 Reply Likes
We are following the crash reports for this MacOS 10.11 issue (and it really is just 10.11.x), but are still waiting to hear back from Apple about the cause and possible ways to work around it.
Photo of sam ashley

sam ashley

  • 2 Posts
  • 0 Reply Likes
This has been happening for over 4 months. Shouldn't Adobe be trying to figure the cause themselves?
Photo of Chris Cox

Chris Cox

  • 20280 Posts
  • 815 Reply Likes
We can't find anything in our code that could explain it, and it appears to be an OS bug, so we have to wait to hear from the OS vendor.
Photo of Paul Vlachos

Paul Vlachos

  • 2 Posts
  • 0 Reply Likes
Mine worked perfectly for a week - I finally upgraded from CS6. Then, as soon as I upgraded Bridge CC yesterday to the newest version, it immediately failed to launch. I run the latest version of the Mac OS, by the way. I just copied a version from last week that I had backed up and it's working flawlessly again. I'm not so certain the OS has anything to do with this.
Photo of Chris Cox

Chris Cox

  • 20280 Posts
  • 815 Reply Likes
Paul - if your crash is not identical to what is being discussed here, then you need to create a new topic and give details about exactly what is happening on your system.
Photo of Greg

Greg

  • 2 Posts
  • 0 Reply Likes
I am having the same issue with Bridge, using it as an image db for catalog layout with InDesign. So frustrating...I'm an Adobe fan but this is something else...

I cannot upgrade to the latest InDesign due to plugins we are using (and don't want to reinvest $1500 USD for an upgraded version) but this is crashing 10 times a day.

Any news or feedback would be greatly appreciated.

Cheers, 
Greg
Photo of Chris Cox

Chris Cox

  • 20280 Posts
  • 815 Reply Likes
The Bridge team is working with Apple to get this issue resolved.

Unfortunately this site only supports the Photoshop family of products.  For InDesign issues, try posting in their user forums: https://forums.adobe.com/community/indesign
Photo of Greg

Greg

  • 2 Posts
  • 0 Reply Likes
Thanks Chris. InDesign isn't the issue...was just setting an understanding of what's running in case anyone's having an issue that involves InDesign. I didn't think so...thanks for the quick reply.
Photo of jobumac

jobumac

  • 44 Posts
  • 1 Reply Like
I posted the same question in the Adobe Bridge Forum (here https://forums.adobe.com/message/8524770#8524770) and a user (stevew17473063) apparently solved it with unchecking that two monitors/displays use different spaces in Mac OS X (preferences/mission control/ uncheck displays have separate Spaces). It works with Bridge 6.1.1.10 and 6.2.0 - but anyway check if you have the latest version of Bridge (6.2.0).

I also had crashes from time to time since I updated to Bridge 6.2.0 and the mission control option turned off - but considerably less than before (three in one month or so). However these seem connected to XMP metadata, because Bridge always crashed when I wrote information into the metadata (picture or file information, which opens with cmd + I).

So first step: give it a try with the first mentioned trick ... good luck!
Photo of Chris Cox

Chris Cox

  • 20280 Posts
  • 815 Reply Likes
Yes, that is a workaround for the time being (and the same OS bug may be causing crashes in other applications).
Photo of Darren Russinger

Darren Russinger

  • 4 Posts
  • 0 Reply Likes
The workaround from Adobe sucks.  I've had Adobe personnel tell me that although they were aware of this issue, it was Apple's problem to fix.  I've had Apple look at my system files and tell me that Adobe is working on it.  Abobe points me to Apple, Apple laughs and says "nice try Adobe".  Pull your head out Adobe!
Photo of Chris Cox

Chris Cox

  • 20280 Posts
  • 815 Reply Likes
It actually is a rather common MacOS 10.11 bug, and Apple is working on it.  Yes, only Apple can fix this issue in the MacOS code.
Apple support personnel have no visibility into Apple's bug database, so they don't know what Apple is working on.

In the meantime, the workaround should avoid the OS bug until Apple can release a fix in an OS update.
Photo of Darren Russinger

Darren Russinger

  • 4 Posts
  • 0 Reply Likes
There is no workaround for a single monitor...other than not using Bridge.  
Photo of Chris Cox

Chris Cox

  • 20280 Posts
  • 815 Reply Likes
Make sure you install the MacOS 10.11.4 update.
Photo of grauenwölfe

grauenwölfe

  • 216 Posts
  • 81 Reply Likes
Apple support personnel have no visibility into Apple's bug database, so they don't know what Apple is working on.
Even as a typo this is incredibly accurate.
Photo of Deepak Gupta

Deepak Gupta, Employee

  • 7 Posts
  • 1 Reply Like
Official Response
Hi,
This crash issue has been fixed in Bridge CC 2015 patch update released on 19 Sept. The patch build number is Bridge 6.3.1.186

Thanks