Copy link to clipboard
Copied
Last week I posted a thread regarding huge resource spikes when using Adobe Bridge 2023 on macOS:
A few minutes ago I was greeted with this message regarding my system running out of application memory and my hard drive running out of space (attached). In this case it looks like Adobe Bridge was using 123.22GB of memory.
Again, any insights as to why this is happening and what I could do to prevent it would be greatly appreciated. Thanks!
Thanks for providing feedback. From our initial investigation, either the Bridge cache is missing the required permissions or may have been corrupted.
Could you try the below steps and confirm if this helps the issue that you are facing:
Regards,
Navkamal
You're skirting around the real problem. The resource management of the latest versions of Bridge is terrible. If you want to fix the issue, rewrite it from scratch.
Until last month, I used Bridge on a 2014 Mac with the same resources. OSX Sierra and Bridge 2019.
Bridge was fast. I keep several tabs opened, switching and copying from one to others and creating thumbnails up to 5GB. I always had several apps opened. Bridge NEVER went out from application memory.
Now, I tried all available versions
Copy link to clipboard
Copied
This is happening to me now: 160GB.
I've had this memory vampire thing happen on many of Adobe apps using massive memory when there's not even a file open in the apps.
The only resoltion I had was to uninstall the apps and reinstall.
MacBook Pro M1 Max, Ventura 13.3, Adobe Bridge v13.0.3.693
Copy link to clipboard
Copied
same here, using iMac M1 2021 16GB RAM
everytime when I leave the Adobe open for a few hours, it run out of memory, saying the usage is around 80GB, i need to force quit the appliction to release the memory
Copy link to clipboard
Copied
Add me to the list of M1 Mac 16G users who are experiencing this problem (see image below). It is quite apparent from the length of this thread and the fact that it is over 5 months old that Adobe is Well Aware of the issue and does NOT have a solution forthcoming. They have not even posted a notice of their recognition of the problem. Having been a Adobe user for the past 26 years, I do not know where to turn for a better product. At this point, my solution is to terminate the Bridge and photoshop program(s) at the end of each image processed.
Copy link to clipboard
Copied
Copy link to clipboard
Copied
Same for me Ventura 13.3.1(a) M1Pro 32GB.
Bridge 2022 works without any issues, which is why I've made a request to make Photoshop 2023 work with Bridge 2022, otherwise we can't use it in a professional environment.
Seriously Adobe Support, this has been an issue since day 1 of Bridge 2023 being released, if you can't fix it - fine. But please give us Bridge 2022 with compatibility for Photoshop 2023 in the meantime. That's not too much to ask.
Copy link to clipboard
Copied
I wish I could explain why I am not getting the terrible resource spike that you're getting on my Mac Studio. For me, I'm seeing nothing abnormal; it's just working as one would expect or hope. I leave Bridge on all the time; I've no answer or suggestion on that.
However, as far as working with Bridge 2022, and not having Image Processor, actually you do. If you go into Photoshop, you do have File (menu) -> Scripts -> Image Processor. That's the same one found in Bridge, PS installs that into Bridge during instillation. When installing Bridge and Photoshop, Photoshop looks to see (1) if Bridge is there and (2) if it's compatible with that version of Bridge. If it passes those two conditions, PS installs the scripts. However, that doesn't prevent you from using Image Processor in PS.
Yes, it's not as efficient as using it from Bridge, but it does let you use Bridge 2022 and PS 2023.
I hope that helps.
Copy link to clipboard
Copied
Well if it's not as efficient then it's not quite the same. Likewise when doing panorama-stitches or stacking in PS you have to first find the folder, select the images etc - all that is very frustrating and time consuming.
Just as a friendly reminder: This is not freeware. We're paying for it.
Copy link to clipboard
Copied
@CMB_photosnapper at no time did I EVER suggest that this was a permanent solution. I suggested a temporary alternative that does work. If you are not interested in workarounds for temporary solutions, please let people know.
Copy link to clipboard
Copied
@gary_sc I know, I'm sorry if this sounded rather curt but I've been using this workaround for months now, actually more like half a year.
Personally I don't even use Lightroom but Bridge and Photoshop are an absolute necessity and seeing how poorly Bridge is being serviced/updated/fixed is very, very taxing and annoying.
Apologies.
Copy link to clipboard
Copied
@CMB_photosnapper apology gladly accepted.
I'm glad that you do know the workaround.
FWIW, I do have a smidgen of contact with some of the Bridge team, and I do know they are working very hard in trying to resolve all of these issues. Unfortunately, I do not know anything about programming, so I cannot begin to understand why all of these issues are taking so long. But, then again, my wife doesn't understand why it's taking me so long to build the furniture I make for us. (LOL).
I do wish I knew more about what's going on, but I don't.
Copy link to clipboard
Copied
I do know quite a bit about programming. They have to be able to reproduce the problem to fix it. I've given them as much technical information as I can. They reached out asking questions and offered a screen-sharing session to see it. I've offered to load up test software to get them more information.
There are a lot of variables involved like what plugins do you have installed. How much Photoshop/Bridge history garbage is in the registry (Windows term, Defaults on a Mac). Each app has a database of settings that collects garbage over time and may need to be purged and you don't know exactly which change caused it.
Then software development goes through a process where a bug is reported, it gets ignored because it's just not a high priority against other bugs and it takes time for those experiencing to report it. One or two reports of an issue is hardly worth chasing down, but when 10 people are complaining about it, now you have a potential problem. It takes the Program Owner (a role on the team) to schedule the work with the team. The next phase is "We can't reproduce it" and they hope it goes away, but the customers keep complaining, and it finally gets some real engineering effort behind it.
I know this sounds negative toward development teams. It's not meant to be that way. Adobe has millions of customers and thousands of reports that they have to go through. They don't have infinite staff, so the amount of effort that goes into an individual problem has to be properly scaled and resources allocated correctly. It's a hard problem. Engineering teams want to help everyone. They want their software to be perfect, but the reality is that problems get prioritized. They can be difficult to reproduce. You can't fix it if you can't find it, so we just have to be patient and stay working with them.
Copy link to clipboard
Copied
Copy link to clipboard
Copied
Hi, I have the same problem on my Mac Pro, M2, 64Gb RAM
The only solution which I found currently to do: Adobe Bridge 2023 - Settings - Cache Management - Purge All Local Cache Files (it's will delete cache from Adobe Bridge, so thing twice if you need it), after it it's working well
Copy link to clipboard
Copied
Thanks for providing feedback. From our initial investigation, either the Bridge cache is missing the required permissions or may have been corrupted.
Could you try the below steps and confirm if this helps the issue that you are facing:
Regards,
Navkamal
Copy link to clipboard
Copied
thank you for that suggestion. I'll report back and see what it does.
What I can tell you is that even though all previews etc are rendered and Bridge should be idle, it's always using the CPU in the background.
Could you tell me: Does Bridge create a file index of sorts in the background?
EDIT: or does it keep the CPU busy to avoid getting put into standby/sleep mode?
I really don't like that, this will cause unnecessary system ressources to be used and worst of all it'll drain the battery when workout outside away from an outlet.
Right now I have Bridge runing in the background, only accessing one folder (which should have all its files already rendered), no images are selected, no images are opened in Photoshop.
Activity Monitor is actually says Bridge is using 140 - 300% CPU (sometimes more) in idle, meanwhile Photoshop in idle uses around 1% or less.
I previously mentioned that Bridge is the only application I've come across that causes coil whine on a Apple Silicon chip - and I suspect that constant CPU usage is a symptom of these issues. I'm not that technically savy but I would assume that there's a problem with the communication and the command prompts that are sent to the CPU, maybe an issue with sleep/wake signals where the systems wants Bridge to give up some system ressources but Bridge keeps clawing them back? Or it really does try to create an index but keeps failing?
Copy link to clipboard
Copied
Copy link to clipboard
Copied
Great that worked.
After openening a folder it fills cache for the pictures on screen and than cpu is low.
Thanks, Hans
Copy link to clipboard
Copied
@kuppj00 could you tell me what your CPU usage is according to Activitiy Monitor?
Copy link to clipboard
Copied
It was 1,9% the first time but now again afeter opening the same folder again around 200%
Copy link to clipboard
Copied
The first tine a folder is cached it works fine but when you come back to a previously filled folder cpu stay high around 200%.
Unsure what it does then.
This only happens if it is a directory with ACR and JPG in the same directory.
Copy link to clipboard
Copied
Thank you.
I have the same issue with a folder with TIF files.
Copy link to clipboard
Copied
I tried your recommendation. However, I opened up to find Bridge, again, using high RAM: 202.43GB.
Sidenote: PS Beta is using a lot for having one small jpg (single layer) open. I've had this issue with all Adobe apps have been running ammuk, at one time or another, or at the same time. So tiresome.
Copy link to clipboard
Copied
Maybe this is somehow connected with another issue;
I found the culprit for the high CPU usage: The folder panel.
I assume Bridge is trying to access/read stuff that is visible in the folder panel, even if those folders or drives are not opened in Bridge. Maybe (!?) that caused the Cache to go haywire after some time with the absurdly high memory usage, CPU usage, coil whine etc all and finally leading to a corrupt cache after a while?
Copy link to clipboard
Copied
I have the same problem on Windows too. My workflow is now unusable because my system is running so slowly.
Copy link to clipboard
Copied
M1 ULTRA (MacStudio) / 128GB RAM / Bridge Ver 14.0.0.102
I am experiencing memory leaks with this setup. This memory leak has been occurring ever since Bridge updated its UI. As shown in the attached image, Bridge demands memory beyond the installed RAM, creating a very large SWAP file.
This happens even when no operations are being carried out. I've tried uninstalling Bridge along with its preferences and reinstalling it, and also deleted all cache files (there's no folder named v36). But even if it seems to be fixed temporarily, the issue suddenly reappears. This happens even if the only files in the open folder are TIFFs or JPEGs.
I've never encountered an application that behaves this abnormally.
Because of this, I have set up Keyboard Maestro to check the memory usage of Bridge every few minutes, and if it exceeds 20GB, it sends a "quit" or "kill -9" command.