Photoshop/Bridge: PC locks up on starting CC apps

  • 1
  • Problem
  • Updated 4 years ago
  • (Edited)
First noticed with Bridge CC now also with Photoshop CC since latest update
About 30secs after starting Bridge, disk transfer light comes on continuous and PC then responds very slow.
Lasts about 4 minutes, thereafter PC operates normally.
Appears to be a Creative Cloud issue as this does not occur with CS6 version of Bridge.

PC is running 64bit windows7.
Have just Photoshop and bridge installed via CC.
Lightroom does not show the symtom and was installed before joining CC.

On further investigation: note in Task manager that little disk or cpu activity is occurring.
The IO seems to be logged under I/O Other which suggests app may be performing some kind of system/gpu performance test.
Am assuming that Adobe engineers will know immediately from the design what the app is doing.
Note this happens in both Bridge and Photoshop and means both are locked and unusable for some 5 minutes.
As far as I am concerned this makes the apps absolutely useless.
Photo of Geoffrey Phillips

Geoffrey Phillips

  • 15 Posts
  • 0 Reply Likes
  • deeply annoyed

Posted 4 years ago

  • 1
Photo of Jeffrey Tranberry

Jeffrey Tranberry, Sr. Product Manager, Digital Imaging

  • 13977 Posts
  • 1670 Reply Likes
Hi Geoffrey,

When you say latest update, do you mean the latest update to the Creative Cloud application? Or an update to Photoshop or Bridge?

In any case, what version of the CC app do you have installed? (Version 1.5.1.369 is the latest)
Photo of Geoffrey Phillips

Geoffrey Phillips

  • 15 Posts
  • 0 Reply Likes
What I meant was the latest updates available for CC (Version 1.5.1.369 released on 3/21/2014), bridge cc, and photoshop cc (CC shows these as up to date).
Also for windows, nvidia drivers, I basically take every official update offered with the sole exception of Flash player.
Do not have the Camera Raw RC1 update that is pending.
Re:favorites in explorer. shows just the Downloads folder, recent places and desktop. Problem still there afer clearing recent places.
Noted that the Disk light stays on for the 4+mins even if Bridge is closed!
Imples bridge has triggered some thread that runs to completion independantly.
Note Bridge CS6 does not do this. It has to be something that has been added to the CC versions of Bridge and Photoshop.
Photo of Jeffrey Tranberry

Jeffrey Tranberry, Sr. Product Manager, Digital Imaging

  • 13977 Posts
  • 1670 Reply Likes
If you launch Photoshop CC by itself (and not launch Bridge) does Photoshop launch and load normally? Or is there a huge delay launching just Photoshop?
Photo of Geoffrey Phillips

Geoffrey Phillips

  • 15 Posts
  • 0 Reply Likes
Jeff,
No I it happens everytime launching Bridge CC or Photoshop CC standalone.
Bridge appears to do some checking of various folders inc the current active folder displayed and its while this is happening that it goes into the lockout state.
It doesn't come to a sudden stop, instead it tails off into more normal disk activity as it finishes the folder checks.
Looks to me as it its something early in the checking sequence that triggers the problem.
Have since had Resource Monitor running when testing this.
In the Disk tab under Storage the C drive is at 100% usage.
Its not showing clearly which process/thread is causing this.
This is not a tool I am familiar with, but it looks like some high priority system process is hogging the disk as the processes listed under Disk Activity are showing disk response times of several seconds.
Have tried this with the Norton Antivirus and firewall disabled with no effect.
If run with no internet connection the adobeCC background helper processes do not run so can rule them out. Symptoms are the same with or without an internet connection.
Photo of Chris Cox

Chris Cox

  • 20280 Posts
  • 766 Reply Likes
What you are describing sounds a lot like a failing disk drive, or some utility on your machine messing up disk activity (antivirus, backup, "disk optimizer", etc.).
Photo of Jeffrey Tranberry

Jeffrey Tranberry, Sr. Product Manager, Digital Imaging

  • 13977 Posts
  • 1670 Reply Likes
Let's try debugging Photoshop by itself more. Have you tried restoring Photoshop prefs? http://blogs.adobe.com/crawlspace/201...
Photo of Geoffrey Phillips

Geoffrey Phillips

  • 15 Posts
  • 0 Reply Likes
Jeff
OK reset Photoshop prefs by moving the file.
Sorry but has had no effect.
Photo of Jeffrey Tranberry

Jeffrey Tranberry, Sr. Product Manager, Digital Imaging

  • 13977 Posts
  • 1668 Reply Likes
Hmm. OK.

Does boot into Safe Mode have any effect? http://blogs.adobe.com/crawlspace/201...

What about a new admin user account?
http://blogs.adobe.com/crawlspace/201...
Photo of Geoffrey Phillips

Geoffrey Phillips

  • 15 Posts
  • 0 Reply Likes
Jeff,
Following your note, have tried disabling the startup services and processes.
No progress. Will try safe mode.
May I remind everyone this is shown by either BridgeCC or Photoshop CC run in isolation.
The CS6 versions do not show this problem.
In other words its something common to CC that has been added since CS6.
You seem to be saying its my system, but if it is then why do the CS6 versions run OK?
Photo of Geoffrey Phillips

Geoffrey Phillips

  • 15 Posts
  • 0 Reply Likes
Jeff,
Progress do not see the problem in safe mode.
Photo of Jeffrey Tranberry

Jeffrey Tranberry, Sr. Product Manager, Digital Imaging

  • 13964 Posts
  • 1662 Reply Likes
OK. So there's some driver or utility that's interfering with the Apps.
Photo of Geoffrey Phillips

Geoffrey Phillips

  • 15 Posts
  • 0 Reply Likes
Jeff,
Following your note further, have uninstalled Bridge and Photoshop CC versions.
Reinstalled PhotoshopCC on my second disk.
This so far seems to run OK.
So assuming installing BridgeCC doesn't cause any problem we can regard the problem resolved. Though means have no real idea what was causing it.
Either way thank you for your advice.
Geoff Phillips
Photo of Jeffrey Tranberry

Jeffrey Tranberry, Sr. Product Manager, Digital Imaging

  • 13977 Posts
  • 1668 Reply Likes
Hi Geoffrey, indeed this was a strange one. I hadn't seen any other reports like yours, so not sure what went wrong. Hopefully things are back to normal after reinstall. Let us know.