Camera Raw: Editor hangs Photoshop after latest update in August 2017

  • 3
  • Problem
  • Updated 1 year ago
  • (Edited)
The Camera Raw editor now  hangs Photoshop after the latest update on August 2017. I have to terminate Photoshop. Any suggestions as to what might be wrong? How do I fix this problem?
Photo of James R Kochanowicz

James R Kochanowicz

  • 6 Posts
  • 1 Reply Like
  • Angry and frustrated

Posted 1 year ago

  • 3
Photo of Cristen Gillespie

Cristen Gillespie

  • 1375 Posts
  • 379 Reply Likes
 Could you be more descriptive? What OS are you using? What versions show up in your About screen for both apps?  Also, when you say it "hangs" Photoshop, do you open an image from Bridge or from Photoshop, and if you open from Photoshop, have you tried opening from Bridge to see if that does the same thing? Or is the issue only that upon opening the image from Camera Raw INTO Photoshop, that Photoshop hangs, and where you open from is irrelevant?

There are so many variables here that could be affecting behavior, it's important for Adobe to know as much as possible when they try to figure out what the problem is. FWIW, I'm not having any problem at all with editing photos in CR and opening them in 2017. Mac running El Capitan.
(Edited)
Photo of Michael Harris

Michael Harris

  • 5 Posts
  • 1 Reply Like
For me m using w10 no issues prior to ACR update. ACR opens and performs normally until edit is complete and I click on button which should return me back to PS but it just hangs with no response to any commands. I need to close via Task Manager. Sorry but away fromPC at present.
Photo of Cristen Gillespie

Cristen Gillespie

  • 1375 Posts
  • 379 Reply Likes
Camera Raw should open in any version of Photoshop that is currently running. If no version of Photoshop is running, it's possible Camera Raw is looking for a version that it (Bridge or quite possibly Windows) doesn't have set as the default for CR to open with.

I'm not saying that's it, but I've heard reports like this before (even had it happen to me once) and it often turned out that the OS and/or Bridge couldn't find the right version to open. It's also possible that Preferences are no longer valid with this new version of CR.  So to troubleshoot, one thing you can do is launch Photoshop before running Camera Raw to see if that helps. And a couple of places you can check are Bridge's File Associations to make sure the version of PS you want to open is selected as the default—and the same with your Properties (it used to be called) in Windows.

And if those are correct and as expected, deleting Preferences for Bridge and/or Photoshop might fix the problem. However, before you delete Prefs for either, be sure you make a backup copy so you can easily put them back if fresh preferences doesn't fix anything, and be sure any custom Presets and Actions have been saved out to disk, so you don't lose those.

Since I'm a Mac owner, I'm not aware of any particular issues with Windows (Win 10 seems to be as full of problems for PCs as Sierra has proven to be for Macs), and you may want to wait on deleting Prefs for an Adobe person to step in. They may know about other Win10 users having the same problem, or be able to suggest another way to troubleshoot. However, it won't cost you anything to launch PS and see if Camera Raw can then find it and open the file in PS.
Photo of James R Kochanowicz

James R Kochanowicz

  • 6 Posts
  • 1 Reply Like
I updated my AMD display driver; the display driver was released on 08/23/2017. Did Adobe tell them about the problem? If so, it would have been helpful for Adobe being proactive about telling its installed based. 

This resolved my issue.
(Edited)
Photo of Michael Harris

Michael Harris

  • 5 Posts
  • 1 Reply Like
Hi Cristen,

Thanks for taking the time to reply. Although I did once suffer from the problem you describe, this is not what is happening now. It doesn't matter whether I open a RAW file from Bridge or PS direct, the problem is the same. I perform the edit as necessary within ACR but after selecting either 'done' or 'open' Photoshop then hangs, in as much as it loses focus and no selections or commands are available and eventually I have to quit by invoking task manager. I hope that makes it a little clearer. All the best, Michael
(Edited)
Photo of James R Kochanowicz

James R Kochanowicz

  • 6 Posts
  • 1 Reply Like
Please, try to updated your display driver to the newest verision. Do you have an AMD graphics processor.
Photo of Michael Harris

Michael Harris

  • 5 Posts
  • 1 Reply Like
I have found a resolution. https://forums.adobe.com/thread/2360284 The answer was to turn off GPU accelerator. 
Photo of Cristen Gillespie

Cristen Gillespie

  • 1375 Posts
  • 379 Reply Likes
> The answer was to turn off GPU accelerator. >

Odd. This thread seems to be mainly about not seeing the same thing in both apps, but not about not being able to open them and freezing PS, but since turning it off worked, that has to be it. That must be the most delicate setting in both apps, since it seems to be as responsible for problems as Preferences.  I don't know how it's got its tentacles into opening files from Camera Raw, though. Weird, since right before the update, you weren't having this problem.

I'm glad you found an answer. Now to find out what you can do about this to fix it. It sounds like it must be a bug?  At least you can keep working until Adobe responds to this.
Photo of James R Kochanowicz

James R Kochanowicz

  • 6 Posts
  • 1 Reply Like
I updated my AMD display driver and this resolved my issue in using Camera Raw.
Photo of Michael Harris

Michael Harris

  • 5 Posts
  • 1 Reply Like
Yes, they were slightly different issues but with the range result. I must say that it seems much slower to process. I will try and then on again at next update. Thanks again for your support.
Photo of James R Kochanowicz

James R Kochanowicz

  • 6 Posts
  • 1 Reply Like
Try updating your display driver to the latest version. Do you have an AMD display driver.
Photo of James R Kochanowicz

James R Kochanowicz

  • 6 Posts
  • 1 Reply Like
I updated my AMD display driver; the display driver was released on 08/23/2017. Did Adobe tell them about the problem? If so, it would have been helpful for Adobe being proactive about telling its installed based. 

This resolved my issue with using Camera RAW.
Photo of Michael Harris

Michael Harris

  • 5 Posts
  • 1 Reply Like
Great find James, I will try the same tomorrow. Thanks for sharing. I am on mobile phone now. Unsure what graphics card I'm using off hand.
Photo of Cristen Gillespie

Cristen Gillespie

  • 1375 Posts
  • 379 Reply Likes
> I updated my AMD display driver; the display driver was released on 08/23/2017. >

Mac folk can't resolve issues by updating their drivers. Apple decides when that happens, so unfortunately, we don't have that avenue to explore, but Windows users can.

Your solution appears to be a common enough response from Adobe when troubleshooting for Windows, so maybe the routine is "disable GPU acceleration—if that fixes it and you're on Windows, look for an updated video card driver." I can understand that there's no way Adobe could possibly take the time to test every OS version and video card/driver combination to know when we can expect a fail, unfortunately.  I suspect it's not something they can know in advance—the best they can do is detect that your card/driver isn't one of the ones they no longer support at all.

Knowing what I was looking for now, I googled the problem with the GPU settings and video card drivers:

https://helpx.adobe.com/photoshop/kb/troubleshoot-gpu-graphics-card.html

Pretty interesting how much winds up related to this.

"Crashes, performance issues, or incorrectly-rendered windows or objects, redraw issues, or artifacts in Photoshop. See the Graphics processor (GPU) troubleshooting steps below to resolve these issues.
Experience crashes, performance issues, or incorrectly-rendered windows or objects, redraw issues, or artifacts in Adobe Camera Raw. See the Camera Raw graphics processor (GPU) FAQ for additional troubleshooting information for these issues."

Incorrect rendering and artifacts are easy to understand, but crashes and performance issues are great big buckets that anything at all to do with the apps and/or the hardware could be causing.<sigh>