Known Participant

Answered

Adobe Bridge 2023 using 123GB of system memory on macOS

Forum|Forum|3 years ago
December 15, 2022
18 replies
24638 views

Last week I posted a thread regarding huge resource spikes when using Adobe Bridge 2023 on macOS:

https://community.adobe.com/t5/bridge-discussions/averaging-700-800-cpu-usage-on-adobe-bridge-2023/m-p/13403193

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!

This topic has been closed for replies.

Correct answer Roberto Bigano

Hi @robmiracle

Since we are not able to reproduce the issue at our end, could you please share a few more details to help us investigate the issue..
- What is the average size of NEF file

- Are you using any other application along with Bridge and is the memory usage for other applications is also going high

- Also what operations you are trying on Bridge

Regards,

Bridge Team

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 of Bridge and all settings without success. I'm an expert user.

Additionally, in Bridge 2024, the Search option doesn't work.
I must use the previous versions.
It must be corrected that Adobe wastes users' time checking the settings.
The problem is on your side.

Last, Photomechanic is not an option. Price apart, it doesn't read PDFs nor fit with my Photoshop workflow.

B

Bamwhochi

Participant

The problem with "renaming the folder " is that when you launch bridge again , it re writes another "v36 folder" and the problem keeps happening - how do you make the usable folder , the one you told us to re wrtie ?

is there a terminal prompt we can use ? this kills our entire sytem and has to shut down

D

donna mf63427830

Participant

Same here. Brand new M2 mac Studio Ultra with 128 gb of ram. New install of everything.

Currently on Sonoma 14.2.1 . Bridge version 14.01.137

This NEVER happened on my older iMac 27" with 64 gb of ram with that system running Ventura 13.4.1 (c)

P

PatsaphotoG

Participant

I'm on a 2021 Apple M1 Pro, running Sonoma Version 14.0 and Bridge 14.0.1 and I just had a system notification that I ran out of disk space and the pop up window showed Bridge was using 75GB of space. This has gotten out of hand.

Yamonov

Legend

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.

--Yamonov

M

macz5024

Known Participant

Same problem with MacStudio on Ventura 13.6.1; 64 GB RAM. Bridge 2023 almost killed my Mac – filling up 230 GB with just nothing but??? I immediately removed it and will not use it again. I am glad I am already PhotoMechanic for years...

P

paulv@panix.com

Participating Frequently

I have not had the problem in a while, not since a few weeks after I reported it here initially. What I did as a workaround is to just quit Bridge after every time I use it.

My latest problem is with the Photoshop tool bar disappearing, but that's for another day and another thread.

G

Gerard317969186ssr

Participant

I have the same problem on Windows too. My workflow is now unusable because my system is running so slowly.

C

CMB_photosnapper

Known Participant

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?

N

Navkamal Rakra

Adobe Employee

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:

Quit Bridge if it is running.
Go to /Users/<username>/Library/Caches/Adobe/Bridge/Cache folder
Rename v36 folder to v36_backup
Launch Bridge again

Regards,

Navkamal

C

CMB_photosnapper

Known Participant

@Navkamal Rakra

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?

A

Aleksandr29501932bqt7

Participant

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

nickm47716398

Participant

Same here Montery 12.2. Lifetime user never shut bridge. Basically have had a consistant bridge window open since 2005. Came back tio the studio today to a warning on the screen about Bridge consuming over 200 gigs. Sounds like it is patch or update time. Right Adobe?

C

CMB_photosnapper

Known Participant

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.

gary_sc

Community Expert

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.

M

Mark Zealor

Participating Frequently

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.

Show more replies

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded