Camera Raw Crashes, and has been bad for months! 3 months with no solutions!

  • 2
  • Problem
  • Updated 3 years ago
The issues started the last week of October 2015.
My system is a Mac Pro six core (5.1), 48 gigs of RAM, with the operating system on a SSD, and the scratch file on an SSD.

Workflow is this. A client brings memory cards, and external drive to me. In bridge we choose the images to be worked on, and copy them onto his drive (USB3). Then through bridge we open the images in a group (about 10 of the time), make our basic changes, then save them off as 16-bit TIF files. Any images that require heavy editing is done in Photoshop. The photographer will organize, and rename the photos, based on his clients expectations. Then again in bridge we open the images and save them off in smaller versions, that he gives to his end client (usually an architect).

bridge would occasionally crash, but usually just starting the computer fresh, or clearing out the memory, would solve this. However in October it crashed multiple times. This was just after I updated. I tried all of my trips but nothing worked. So on November 3 I called Adobe's help line. They gave me some new things to try that seemed to help, but didn't solve the problem. They suggested that I continue and that an update would be coming. The strange thing is they closed my case, even though they knew that they had only given the temporary solutions (0187215514).

Update did come, but it did not fix the problem. So I called again. they tried several things all of them seem to help but none of them solved the problem. again they closed the case (0187215731).

Then at the beginning of December nothing seemed to work (new case 0187370127). camera raw would crash about 50% of the time. And my clients were getting very frustrated at how long it was taking me to turn around their images. Again I called the helpline. They told me that it was a conflict with El Capitan, and that they would get back to me with solutions. We went back and forth for several weeks, and ultimately I was advised that my video card was not supported in that I needed to upgrade. So I did. Guess what it made absolutely no difference! $350 down the drain. I called again, and again, with my clients angry and no solution in sight, I went to Apple to have my machine examined and possibly go back to Yosemite operating system. it took me all weekend, but I got my system checked with a clean bill of health and back to Yosemite.

It still didn't work! So now the tech told me to uninstall bridge, and reinstall an older version.

Any guess whether it worked? You got it NO!!!

SO I have no alternative but to go on these forums, and hope that someone has a possible solution before I lose my clients. this is already cost me hundreds of dollars in lost time, and hundreds of dollars in equipment that I didn't need to replace. But if I lose a client that will cost me thousands. I can't believe that a company like Adobe would create software for working professionals that was so completely unstable, that it would take them months and months to come up with a solution.
Photo of Dennis Watts

Dennis Watts

  • 1 Post
  • 0 Reply Likes

Posted 3 years ago

  • 2
Photo of Michelle Qi

Michelle Qi, Employee

  • 14 Posts
  • 5 Reply Likes
Hi Dennis,

I am sorry about your experience. In order to help you better, would you please send me an email at If you have a crashlog, please attach it, otherwise any details/files you could provide to reproduce on your system? I will work with you offline to get you back on track.