I received a Windows 11 Bridge update today to version 14.1.2.300. It provides no fix to the issues described in this thread. ... View more

I've tested this in the past, but can find no effect from the "Preview Quality: High" option in Bridge. When this option is on, it seems to consume some extra CPU, but with no benefit. The actual preview jpeg files in the cache are no different. The bugs discussed in this forum and others remain the same. So leave it off. ... View more

Ditto the OP. Two bugs, actually. The "Generate Monitor-Size Previews" bug is still active on my Windows 11 system under the latest version of Bridge (Version 14.1.1.274). My 2560 monitor gets 2048 size files in the cache, unless I do the toggle trick jjohanson describes.   Second bug is more bothersome and a bit strange. 100% Previews on my 2560 monitor are sometimes soft and pixelated. Sometimes, but not always. I've determined that such bad previews are dependent on image size. Larger images are always OK, but smaller images are not. For me, the problem occurs somewhere around the 5000 pixel (long side) size. Strangely, soft previews occur only on the first display of a preview. If I escape out of a soft preview and immediately come back to 100%, then it's OK. But if I close bridge and re-launch, the soft previews are back. If I trick bridge into actually making 2560 screen size previews, the soft 100% previews still occur.   Another symptom of the bad previews is that when I click on the initial "fit" preview to go to 100%, the preview will jump to somewhere other than where I clicked. Click in and out of 100% and the preview continues shifting off the click point. But again, escape out and come back in, all is OK.   The soft, pixelated previews are a sign of some bad algo that is uprezing a smaller version. Either the 2048 version or the 2560 version, makes no difference. Why it gets corrected to a good preview on a second and subsequent display is a mystery. Why is goes back to soft previews after a relaunch of Bridge is an equal mystery.   I discovered this recently when processing a fresh batch of images from my wife's Sony P&S camera. It has "smaller" images compared to my Canon full frame cameras. In the initial culling pass I was rejecting lots of images because they looked soft. Turns out they were OK, just the 100% preview was soft.   ... View more

The problem of Bridge re-caching and re-generating previews has been around for years. Many old threads in the forums on the issue, yet Adobe coders seem to remain oblivious. On my Windows 11 system, with 50K images spread over hundreds of sub-folders, the problem has been mostly absent since version 14. The problem has always been intermittent, and does not affect everyone. So, it's system dependent. I have long held a theory, and shared it with Adobe, but who knows. In order to decide if cache, thumbnails, previews need be generated, the software has only 2, maybe 3 variables to compare - File Name, Date, and maybe some attribute like format or size. But for an attribute to change the date would also change. So really only 2 variables. You navigate to a folder. The software looks at the files in the folder, then looks it up in the cache. If if does not find the file name in the cache, then generate. If it finds the file name in the cache, is the cache current? How would the software make that decision? Simply by comparing the date/time (modified) it gets from the operating system (Win, Mac) to the date/time stored in the cache. No match, then generate. The rub, I suggest, comes from different formats of these 2 date/time fields plus whatever logic is used to convert one of them to the format of the other for comparison. Imagine the date/time of the OS is kept to a fraction of a second, but the date/time in the cache is not. Now imagine that the processing speed of the computer system is slow or delayed at the time Bridge/ACR/Photoshop create or updates the file. So, the delay or rounding make the date/time stored in the cache slightly different from the the date in the OS. Next time Bridge looks at the file the dates won't match, so Volia!, regeneration. That would explain why the problem is intermittent and does not affect everyone. P.S. Arghhhh!!! To make this post I discovered Adobe has changed the forum name. "forums.adobe.com" no longer exists. Now it's community.adobe.com. So, all bookmarks to old threads are lost. ... View more

Yet another new release Photoshop 25.4.0, still no joy on orphaned jpegs. No mention of that issue in any release notes or known bugs. ... View more

New releases today, Photoshop 25.3.1 and ACR 16.1.0.1728 Sadly, still no joy on the orphaned jpegs from Gen Filled images. ... View more

Creative Cloud gave me an update to Photoshop V 25.3.1 today. So I saved jpegs from 6 different tif images that had Generative Fill applied. Got an orphaned jpeg in the temp folder for each one.   So... problem remains. ... View more

I have a Dell XPS-13 Windows 10 tablet that I have not used for Photoshop for a long time. So I updated its Photoshop to version 25.2 and did some Generative Fill tests. I still got the ".tmp***" folders in my User/Temp directory, but they were empty. No orphaned jpegs there.   JEL says he gets no folders and no jpegs under Win10. I get folders but no jpegs under Win10. But I get folders AND jpegs under Win11. So, it appears to be a Win11 issue, and maybe half an issue on Win10. I imagine JEL and I have enough differences in our Win10 systems to account for that. ... View more

I finally got Photoshop 25.2 via CC (regular update, not Beta). Sadly, the issue of the temp folder jpegs remains. Same as described in my OP.  ... View more

Thanks for the heads up. My Creative Cloud app won't give me an update yet. Probably a staggered release.  ... View more

Eureka! Bridge version 14.0.1.1137 and Camera Raw version 16.0.1.1683 released today (11/10/23). An initial test, browsing 10 folders with 200+ images, and NO CPU PROBLEM! (Shouting intentional). Plus, no re-caching seen.   It took 8 months but they finally got it fixed. Fingers crossed it stays fixed. Bridge is great, but the caching logic is based on some ancient and out-dated structure. I'm sure it's a nightmare for coders.  ... View more

While continuing to poke around with these Bridge problems I encountered a new error I've never seen before (in 20+ years). I had noticed that the NEW Bridge would sometimes regenerate previews as I navigated folders. Not always, and not on all images in a folder. This was a little consistent with ancient history. Updates to Bridge and ACR years ago would sometimes do that - regenerate previews. In fact, there was a time when Bridge/ACR would regenerate previews constantly, over and over again on the same folder. So I tried testing NEW Bridge V14 against OLD Bridge V13 (the last version that worked well). I let OLD Bridge V13 cache a folder of images, then launched NEW Bridge on that folder to see if it regenerated previews. I went back and forth on this, several reps on different folders, looking for a pattern. But I didn't find one. Sometimes NEW Bridge would regenerate previews, sometimes not, with no logic I could see. But then, suddenly, OLD Bridge gave me an error, shown below, saying the cache was bad. I closed OLD Bridge, made a backup copy of my cache, then re-launched OLD Bridge. As promised, it purged the entire cache. Could be a big problem without a backup. My cache is 22 GB, 46K files in 570 folders. It takes hours to rebuild from scratch. And FWIW, all versions of Bridge after V13 ignore the "Generate Monitor Sized Previews" option. They generate 2048 pixel previews in the 1024 cache folder, regardless of monitor size. OLD Bridge V13 correctly generates 2560 pixel previews that match my monitor size. ... View more

We have another update. Photoshop 25 was released yesterday, and a Bridge update to version 14.0.0.102 came along for the ride. The Bridge Beta is still at version 14.0.0.94 and ACR did not change either. ACR still at version 15.5.1.1597.   A test of the CPU problem shows no joy. Still clocking constant CPU when larger thumbnails are displayed. I assume this Bridge update was just to make it integrate with the new Photoshop and nothing else.   I participated in a video conference with Adobe techs a few days ago and was able to demonstrate the CPU issue clearly. They had me email a log file to them, so maybe there is hope. I'm still surprised and confused that they apparently can not duplicate the issue in-house. ... View more

I received email from you saying "We have sent and invite for 10:30 AM US time for Tuesday (5th September)." I responded, "I have no idea what this means. An invite to what?" No word since then. Still no idea what I'm invited to and how I get there. Or which "10:30 AM US time". There are 4 of them. ... View more

Got another update to Bridge Beta today. Now version 14.0.0.94. Still no fix to the CPU problem. Symptoms the same as reported earlier. ... View more

Today (8/13/23) my Windows 11 Creative Cloud offered updates to both the Beta version and the main version of Bridge. The Beta version went to 14.0.0.57. The main version went to 13.0.4.755. I updated both and tested the CPU usage. Still no joy. My Win11 CPU continues to clock forever at 12% to 40% depending on the size and number of thumbnails displayed. And as I reported and demonstrated earlier, it will stop clocking CPU if I reduce the thumbnail size to ity bity and immediately return to an original larger size. But then it starts clocking again when I navigate away from the folder and back again. This link https://helpx.adobe.com/bridge/kb/fixed-issues.html#aug-2023 has notes on fixed issues. It says "CPU usage remains high...", but that line does not link to anything, so I guess that means it is still outstanding. Hard to tell if that means Adobe thinks it's fixed or not. So, Adobe if you are listening, it's not fixed. You're still draining batteries and overheating laptops. ... View more

Another discovery: The "new" Bridge V13.0.3.693 and the Beta are both ignoring the "Generate Monitor-Size Previews" option under Edit/Preferences/Advanced. They are both generating 2048 pixel sized images in the "1024" folder cache, regardless of actual monitor size. All prior versions are OK.   ... View more

A mini update after poking around in the beta version: It appears that the single variable causing the CPU issue is the thumbnail size. On my system, with a 2560 X 1440 monitor, if I set the thumbnail sizes to have a maximum of 170 pixels on the long side there is no infinite CPU clocking. With that small thumbnail size I can display many or few panels, change all preview options, make the Bridge window any size, fool around with other variables, and there is no CPU clocking. But bump the thumbnail size to the next largest option, and CPU clocking starts. There are two root folders in the Bridge cache named "256" and "1024". The jpegs in the "256" folders are all sized at 256x170. The jpegs in my "1024" folders are all sized at 2560 pixels long side because I have "Generate Monitor Sized Previews" set in my preferences. Yours may vary. Do you see the clue? If Bridge is set to display thumbs at 170 or smaller it uses the jpegs in the "256" cache folders. But if you display larger thumbs, Bridge uses the jpegs in the "1024" folders and downsizes them as needed. And something is wrong in that process, causing the infinite CPU problem. I suspect Bridge gets caught in a loop continuously downsizing the "1024" jpegs to fit the selected display thumbnail size. ... View more

Close, but not there yet. The Beta version of Bridge still clocks infinite CPU on my Windows 11 desktop and on my Windows 10 laptop. Here is a 4 minute video demo, hopefully a better description.    https://www.arkacy.com/Other/Temp-Upload/n-5RJTN/i-Z4N8cW3/A ... View more

Same here, but fixed. I launched Creative Cloud. No Photoshop V24 appeared. I opened Photoshop V24 and selected Help/Updates from within Photoshop. A new Creative Cloud window appeared showing both Photoshop V24 and V23, with an update available to V24. I did the update. Re-booted my Windows 11, and launched Creative Cloud again. Now both versions of Photoshop appear. Creative Cloud looks normal. ... View more

  Navkamal Rakra, [abuse removed]. A 5 minmute test on just about any computer would clearly show the problem. ... View more

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. ... View more

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? ... View more

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. ... View more

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. ... View more

Thanks, but I fixed mine by poking it in the eye with a sharp stick. In both Bridge 2022 and 2023, I went to Preferences/Startup Scripts and disabled everything. Shut down, restarted Windows. Back in to Bridge Preferences/Startup Scripts and enabled everything. Close, re-launch Bridge, and Volia!, the Photoshop Tool is back and Load files into Layers is there.   So, basically, I tricked Bridge into reloading startup scripts. YMMV.  ... View more

Ditto here, Windows 11 and all Adobe versions current. Tried to load files as layers for the first time in a long time apparently and found the Tools/Photoshop menu missing. But I kept the old Bridge and Photoshop installed and the Tools/Photoshop is missing there too. I swear it used to be there in the old versions. Maybe installing 2023 messed things up? ... View more