Bridge CS4 - low on memory error

I'm also getting low memory errors when I try to batch process in ACR (eg convert .cr2 to .jpg). If I load 25 files I'll only get half of them done before it runs out of memory and stops. If I then load 25 more I'll only get 2 or 3 done before I get the low memory error. I have to exit and restart before doing any more.

It seems like these errors are very repeatable by many users. I hope Adobe is reading this.

Graduated filter make the same trouble - couple of pictures and LoMem issue is here

it's definitely and Adjustment Brush issue. My ACR and Bridge were just perfect until yesterday, when for the first time, I began using the adjustment brush.

The posts by Curt Young and Don Soloman are very timely. First, Curt is right about Bridge storing data in the central cache (...AppData/Local/Adobe/CameraRaw/Cache). My cache was 1.99 GB and preferences were set at the default value to limit the cache size to 2 GB, so it seemed like I had found the problem. I increased the cache size and I had no more memory warnings. At least not for quite a while. Thanks Curt!

A couple hours later I started to use the adjustment brush in ACR and the low memory warnings started again. I can only use the brush on 2 or 3 images before having to exit Bridge and restart. As near as I can tell this is the only time I'm getting the low memory warnings now. I have a 26" monitor and despite a very fast machine the brush is still somewhat slow and jerky on high quality previews. The adjustment brush is a great idea because now I don't have to use PS in my workflow. However, it looks like Adobe needs to do a little more work to make it right.

One other consideration: LR 2.2 has a well known memory leak associated with the adjustment brush use and with large, multiple file operations of differing kinds. If my memory serves me well, both ACR and LR use the same basic engine under the hood, with obvious differences. They do share the same basic adjustment brush, for instance. So, it is possible that Bridge CS4 also suffers the memory leak problem.

Th adjustment brush in LR2.1 was very slow and jerky--just plain buggy--so when they sped it up in LR2.2, they inadvertenly introduced a memory leak. LR did not have one in 2.1.

For me the adjustment brush is a very weak tool, so I don't use it. I do that sort of work in better applications, like PS for example. I also have no memory problems and I do batch significant numbers of NEF and CR2 files.

These problems are very hard to pinpoint--good luck.

I am certainly not an expert, but I believe the data is stored in a central cache, even though it may export to folders if indicated. I do not know where the memory goes but even a small collection on photos seems like it takes up 6 gig of cache.

I think the Bridge cache is used as a temp dump for files opened, slide shows, edits, and ?. If you are low on memory as least something to think about. Perhaps with 8 gig of RAM those process are carried out there.

I have my preferences set "to automatically export cache to folders when possible," so the 1.3MB cache file is only for the one folder with ~600 raw files.

If your cache folder is only 1.3MB I don't see how anything can work. I have my cache on a 40 gig partition (shared with photoshop) and it has 21 gigs filled, and I rarely open more than one RAW file at a time.

I'm having exactly the same problem. I have an Intel i7-920 processor with 8 GB memory running on 64-bit Vista. After 15 minutes or so I start getting "memory low" warnings and have to exit and restart Bridge. Symptons are as described by Vlad. The folder has ~600 raw files and I have preferences set to "always high quality."

I know that's a lot of memory, but as someone pointed out it should release the memory when it's not being used; instead usage just keeps going up. Also the folder cache is only 1.3 MB. I sometimes get the low memory warning when opening a single image in ACR. Any ideas would be appreciated.

Yesterday I did some extensive search in my photo library - and though no low memory error occurred - all other "low memory symptoms" remained. It typically happened after browsing through app. 1000 images and opening in ACR three - four times a batch with 10-20 shots in one session. In each session I did some common corrections (exposure/contrast etc) incl. some not so common - such as applying graduated filters + some local adjustments (curves/hues/masking). Each time (i.e. after a lot of browsing + 4x opening/correcting app. 20 JPGs (each 15 MPx in size] - I ended with the same result:

-Memory usage more than 1 GB,
-no Low memory error (as mentioned earlier)
-ACR stopped responding to more changes applied to the picture - but did not crash or freeze - just did not display any new changes
-Upon return to Bridge the thumbs were not updated (however were updated upon next restart of Bridge)
-Some images (not all) were unavailable for 100% preview.
-Preview mode (CTRL+B) started to react unpredictably not showing some images, dropping some picures instead of moving around etc.

So the result was not a "crashed/frozen" application just no more working as it should. Restart was necessary and obviously helped.
I think it is necessary to put a heavy load on Bridge to reveal this.