Skip to main content
jaapp88032082
jaapp88032082
Participating Frequently
July 1, 2020
Question

new bridge is not working good and used 100 % of my processor

  • July 1, 2020
  • 4 replies
  • 1984 views

latest photoshop brigde manages to use 100% of my processor while doing nothing special. The new photoshop works properly and uses less than 8% of my processor. Can someone tell me what's going on with that new bridge?

This topic has been closed for replies.

4 replies

jaapp88032082
jaapp88032082Author
Participating Frequently
July 8, 2020

I asked a good IC friend what I could do best to solve the problem of the new version of bridge. He googled a lot and found the solution. Let the processor run out and just leave it on. He has to process all data and that can sometimes take hours. And indeed after 3 hours he was finished. I restarted my PC and bridge worked properly. The problem was solved.
Try it out yourself.
best regards jaap

S
stephenv70437356
Known Participant
July 8, 2020

Thanks for the suggestion Jaap, but I already do that.  I have to, to get the images into Cache.  It hammers the CPU for many hours to cache 2 or 3 thousand RAW files I may shoot in a day.  The annoying part is that this was not the case with Bridge 2017.  It was fast.  Adobe changed the code in some way that has caused its performance to suffer.  This latest iteration also fails when renaming.  It leaves files behind when moving images from one location to another as well.  It fails to delete images.  I can't help feeling that all of these issues are related to way it generates its Cache.

    S
    stephenv70437356
    Known Participant
    July 7, 2020

    Mine does this too.  It has being doing it since CC2018.  It does it when it is creating full res previews from RAW files.  The computer becomes unusable while it does this.  When previewing PSD files, the CPU gets used to around 50% maximum.  When previewing JPEG files it gets used to around 24%.  Previewing around 120 5D Mk IV RAW images takes as long as previewing 24,000 JPEG images.  Something is not right in the code.  I've reported this before for three years now.  Nada from Adobe.  The folks here are not Adobe programmers.  They want to offer workarounds, but I'd prefer my software to be bug-free.

      gary_sc
      Community Expert
      gary_scCommunity Expert
      Community Expert
      July 7, 2020

      Hi Stephen,

       

      You are absolutely correct, we are not programmers nor do we work for Adobe. We're just folks like you who are trying to help folks like you. Just so you know.

       

      As far as software being bug-free, got news for you: I do not think there's ever been bug-free since "Hello World." All software has bugs. The issue is do the bugs interfere with your work? Not all bugs do. The bugs that crash the application are the ones that get top priority.

       

      But again, I do not work for Adobe nor am I an engineer so I have no clue as to where the (documented) slowness is in the fixing cue.

      S
      stephenv70437356
      Known Participant
      July 8, 2020

      And this is the problem Gary.  No-one at Adobe wants to touch these reports.  How did you get the label Adobe Community Professional Gary?  Reply to a set number of posts?  I'm just interested.  It's not an attack on you.

      pcarrizales
      pcarrizales
      Participant
      July 2, 2020

      Same on my Mac, I'm running 10.14.5 this is very frustrating Bridge stops running (bouncing beachball),..I've also run adobe creative cloud twice each time was 45 minutes to an hour to get going.

       

      jaapp88032082
      jaapp88032082Author
      Participating Frequently
      July 2, 2020

      is there nobody with a good answer 

      pcarrizales
      pcarrizales
      Participant
      July 3, 2020

      Exactly 24 hours later and still doesn't work.

      jbm007
      Community Expert
      jbm007Community Expert
      Community Expert
      July 1, 2020

      Which OS version?

      jaapp88032082
      jaapp88032082Author
      Participating Frequently
      July 2, 2020

      windows 10 pro 1909

      jbm007
      Community Expert
      jbm007Community Expert
      Community Expert
      July 7, 2020

      Try researching this topic

      Virtual memory treats your disk as if it is RAM and uses it to swap out temporary files when it runs out of actual RAM. Errors in the pagefile.sys can cause 100% disk usage on your Windows 10 machine. The remedy to this problem is to reset your virtual memory settings.

      Spread  your pagefile.sys over several hard drives.

       

      Another option is:

      Another Windows 10 feature that can cause problems is the Windows Superfetch service. You can disable this service temporarily in a similar fashion to Windows search with the command: net.exe stop superfetch.

      The 100% CPU rise appears to effect some machines alot worse then others.

       

      I have enable both these solutions on my machines.

      Terms & ConditionsAccessibility statement
      Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices