Skip to main content
A
Alfred5E88
Known Participant
March 24, 2023
Answered

Adobe Bridge permanent CPU usage

  • March 24, 2023
  • 23 replies
  • 9387 views

When I let Bridge index a folder of RAW files, initially the CPU usage is high, then it drops after all RAW files have been indexed.

 

But Bridge continues to use 20-25% CPU, even if it apparently is doing nothing. When I exit Bridge (i.e. I close the window), this 20-25% CPU continues in the background.

It only stops when I kill the Bridge process in the task manager.

 

Is there any way to preven Bridge from using 20-25% CPU when it's doing nothing?

    This topic has been closed for replies.
    Correct answer NRC13

    In response to my earlier post, Adobe contacted me and arranged for three of their Bridge team to come online and look at the CPU problem on my PC.  They are aware of the problem and they are working on it.  There was no indication as to when they would have a solution but that will depend on what they find is causing the problem.  Meantime the simple workaround is to use Bridge 12 which is fine.  

    23 replies

    Show previous replies
    NRC13
    NRC13Correct answer
    Inspiring
    June 15, 2023

    In response to my earlier post, Adobe contacted me and arranged for three of their Bridge team to come online and look at the CPU problem on my PC.  They are aware of the problem and they are working on it.  There was no indication as to when they would have a solution but that will depend on what they find is causing the problem.  Meantime the simple workaround is to use Bridge 12 which is fine.  

      grafikundso
      grafikundso
      Participating Frequently
      June 15, 2023

      not bad. 3 months later its still unuseable and burning my cpu. well done adobe....

        C
        Craig Rozynski Shutterfly
        Participant
        June 15, 2023

        I don't want to sound dramatic but it does seem like Bridge 13 was literally giving me headaches.
        Upgraded to Bridge 13.

        Macbook Pro M2 fans struggled to cope with Bridge's excessive processor usage.
        This caused an electrical smell mild enough that I didn't notice, presumably from heated components.
        Others entering my office started commenting on the smell (it's a small space).
        I started noticing an increase in headaches, presumably from the toxic smell. 

        Rolled Adobe Bridge back to version 12.

        Looking forward to a fix in the next version Adobe.

          NRC13
          NRC13
          Inspiring
          May 9, 2023

          I have the same problem in Bridge 13.0.3.   CPU usage is continuously around 40 percent or above regardless of what I am doing. This continues for hour after hour without a break. I have reverted to Bridge 12.0.4 where CPU usage hovers around 2 percent

           

          OS Name Microsoft Windows 10 Home
          Version 10.0.19045 Build 19045
          System Manufacturer Dell Inc.
          System Model XPS 8920
          System Type x64-based PC
          Processor Intel(R) Core(TM) i7-7700 CPU @ 3.60GHz, 3600 Mhz, 4 Core(s), 8 Logical
          Installed Physical Memory (RAM) 16.0 GB
          Graphics card NVIDIA GeForce GTX 1060 6GB

           

          Good to know Adobe are aware of and are working on the problem.

            grafikundso
            grafikundso
            Participating Frequently
            May 8, 2023

            same issue for months. really wondering how adobe can ignore such an issue for such a long time. oh wait, its adobe... 

            H
            Holger24347452umic
            Participant
            May 27, 2023

            maybe adobe is owner of power some powerplants ... 😉

            N
            Adobe Employee
            Navkamal Rakra
            Adobe Employee
            April 28, 2023

            Hi,

            Thank you for sharing your feedback . 

             

            Bridge utilizes CPU to generate cache for the files that are visible on the screen. When the number of files visible on the content panel are reduced by toggling filters in filter panel, the cache generation is stopped for the files that are not visible, hence CPU utilisation comes down.

             

            If you need cache generation to be faster and you do not need previews to be generated beforehand (generating previews also consumes CPU), you can adjust the following settings:

             

            1. Click on the highlighted icon:

             

            2. Select the Embedded(Fastest) option

             

            This should speed up the cache generation for your system.

             

            If you are still facing CPU utilisation issues, could you please confirm if the following Preference in Preferences-> Cache is checked?

            Thanks,
            Bridge Team

            M
            MazStudios
            Inspiring
            April 28, 2023

            This is NOT the CPU idle issues everyone is having. None of theese standard tips is working for this problem. PLEASE tell me you are looking into this problem that is affecting so many?? 

            After talking to your support they confirmed Adobe was aware of the problem. The chat resulted in me having to install v12 again, since none of theese standard fixes apply to the problem. I have the samme settings in v12, and everything works just fine.

            v13 IS broken. Please replay.

            M
            MazStudios
            Inspiring
            April 26, 2023

            Today I finally got some kind of respons regarding this horrible CPU-bug that's been with bridge from the first 13 up till now. I just tried to get hold of support asking them if they are aware of this and if they have a timeframe. After about 30 min, after he tried to help me with stuff thats probably a bug, he answered my initial question with info about Bridge. The team IS aware about the problem apparently and they are working ot it. And that's all I needed to know.

            But. It would be nice if Adobe could have communicated this in the forums since it's such a serious problem and affecting the performance in a huge way. I finally gave up on 13 and installed 12 again. And it was like night and day.

            So. Again. Adobe, please, would you mind communicating a bit more in the forums with us? It's affecting all of our workflows in a big way.

              L
              LarryK_95
              Inspiring
              April 26, 2023

              Your lucky its only eating 20-25% CPU, on all my Macs it uses anywhere from 60-200%. It's been that way for at least the last 3 major versions of Bridge with no indication they care enough to fix it. This is with Bridge hidden in the background with zero interaction with it. The only thing that temporarily fixes it (a few days to maybe a few weeks) is purging all the cache and starting over from scratch rebuilding all your thumbnails.

              R
              redcrown on guard
              Inspiring
              April 26, 2023

              Purging cache didn't work for me on Windows 11. I set up a new cache folder and re-launched Bridge. Let it cache a single temp test folder with 100 tif images. CPU was continuous at +35%. I deleted images from the folder a few at a time. CPU stayed at +35% until I got down to 32 images. Then CPU suddenly dropped to less than 1%. Still no disk or internet activity, so Bridge is just "thinking".

              Did the same test on the temp cache with old Bridge version 12.0.4.286 with no problem. CPU always at less than 1% (after initial caching) regardless of the number of images.

              R
              redcrown on guard
              Inspiring
              April 16, 2023

              This is getting weird. I tested the "panels" theory. No effect on my Windows 11 system. I closed all panels in Bridge, but it kept clocking 35% CPU.

              Then I tried another test. With only Bridge and Task Manager running, and Bridge at constant 35%, I launched my stand-alone HDR programming. It eats max CPU briefly when doing its thing. For the 10 seconds the HDR program was processing, Bridge gave up its CPU and went to less than 1%, while the HDR program was at 97%. When the HDR program finished and went to 0% CPU, Bridge went back to 20%. Not the original 35%. But when I closed the HDR program, then Bridge went back to 35%.

              So I tried it again, this time with Topaz Photo AI. Photo AI went to 30% CPU (and 40% GPU) but Bridge stayed at 35%. So Bridge didn't give up any CPU because it didn't need to. There was plenty available. I don't know much about Windows' priority system, but it seems Bridge is floating at low priority and will give up CPU to anybody who needs it. Still leaves the question of what on earth is Bridge doing. When it's floating at constant 35%, my Task Manager shows zero disk activity and zero Internet traffic. So Bridge is not phoning home and it's not reading/writing to disk. It's just sitting there thinking.

              R
              redcrown on guard
              Inspiring
              April 25, 2023

              Here is another update, in case anybody at Adobe is paying attention. More weirdness on my Windows 11 desktop.

               

              Navigate to any folder with more than 40 images of any type. See Bridge clock a constant +35% CPU. Then display only one image in that folder using a filter (add a label, filter only that label). See Bridge CPU drop to less than 1%. Then clear that filter to re-display all files in the folder. VOLIA!! Bridge stays at less than 1%.

               

              Navigate to another folder and immediately back. See Bridge clock constant +35% CPU again. Filter to display 1 image, <1% CPU, clear filter, still <1% CPU. How weird in that?

                R
                redcrown on guard
                Inspiring
                April 14, 2023

                I recently discovered this too. On a trip with a Dell XPS-13 Windows 10 laptop I noticed Bridge clocking constant CPU after being idle for several minutes. Came home and loaded images to my Win 11 desktop, a monster with 64GB memory and super fast everything. Same thing there.

                Testing showed file types make no difference. Raw, Tif, Jpeg, PSD, all clock 25% to 45% CPU forever when "idle". But I did discover that the number of files in a folder does matter. Less than 40 files, no CPU problem. With 40+ files, CPU starts clocking at about 25% and increases to 45% as the number of files increases.

                I have old Bridge Version 12.0.4.286 still installed on both machines and share cache with the new Bridge. The old Bridge has no problem with infinite CPU usage. So, this makes new Bridge unusable until fixed. I can run old Bridge with the new ACR and Photoshop, but for some unknown reason the new ACR won't launch within old Bridge. But change old Bridge prefs to launch ACR in Photoshop instead and all is good.

                  E
                  enthusiastic_critic1623
                  Participating Frequently
                  May 1, 2023

                  Same as YOU!!!!

                  I check the empty folder in Bridge,CPU clocking less than 3%~5%,that is normality!!!

                  But!!!as soon as I open my photocollection, the cpuclocking skyrockets to 25%-30%or moreeee...~~~even if I do nothing~~~~~~

                  I'm MacBook Pro M2pro,10 cores

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