I'm running Bridge on Windows 7RC and I was experencing same "Bridge low on memory" problems.
Since some folks mentioned Permissions for Users to write to disk I recaled, that my problems started since I moved Cache to another disk.
I've checked out Permissions (disk>Properties>Security) and what I found was that on "Everyone" permission to Write was checked out, But on "Users" wasn't.
So I turned it on and my problems was solved . Since I belive Windows 7 is based on Vista, the solution should be OK for both.
For over 6 months now I have been using CS4 Design Premium quite happily on a 64 Bit Machine with XP64, 8Gb RAM and 3 x 500GB hard drives one of which is reserved for cache purposes only.
In particular I have been using Photoshop and Bridge (the latter is a tremendous package btw) to work on large panoramas compiled using Autopano Giga 2.
However, in the last few days, out of nowhere, I have suddenly been getting the "Memory Low restart Bridge" message. It's as though I've run into the buffers somehow.
I have read the Adobe forums on the matter, tried the various suggestions without success.
For Bridge, the cache size is set to the max. 500,000 items. while in practice it currently contains 11,376 files and 736 folders. I've also set up an additional bridge_overflow folder on the same cache drive the latter being 3% full with 453 Gb free. Finally I did a full CS4 upgrade but still the problem persists.
One interesting thing which may be a clue is that looking at the Properties of the Bridge cache folder it gives two parameters viz Size 2.56 GB and Size on Disk 2.54 Gb which is indicative of a memory limit being approached but I don't see how the former can be increased. Purging the cache folder hasn't made any difference to these values. And finally, I don't know if it is a related problem, but the Loupe quite often states that 100% is unavailable.
Any help / advice would be appreciated.
We also use Shop and Bridge CS4 on two 64x bit machines, like previous mails on this thread we never experienced the problem of the cache on bridge when we were osing CS3 on the same machines. Overall we do prefer CS4, but this bug is very frustrating, neccessitating as it does a complete shut down and restart - with sometimes a complete freeze needing a hard reset. Can you explain a little more re your point about users in XP so that we can try that. Obviously if anyone else is resding this and has any helpful advice, that would be very helpful.
As I see it, the problem is somewhere in understanding of users rights
on disk where cache is located.
In my case the problem was because I didn't have enough rights on drive
where Cache was (wich is stupid since I'm the only user of my comp), so
Bridge couldn't write it's date on target disk).
I don't know for yours , but john-o-eid's problem could be conected with
the same issue. It could happen also in situations when there are
more users and not everyone's rights were assured in phase of CS4
installation, since cache is located by default in folder of user that
installs it. In my case it was
C:\users\daregre\AppData\Roaming\Adobe\Bridge CS4\Cache (in XP instead
of C:\users..., C:\Documents and Settings...).
So either every user must set Cache for himself in his
C:\users\....\Cache directory, or ensure that everyone that uses
computer has WRITING rights on drive where Cache is. So:
1. check out if you've changed settings for cache location, (or someone
2. check everyone's rights on that drive (Control Panel>User Accounts,
perhaps also in disk sharing advanced options).
3. remove every possible restriction of rights for that drive on your
and other common user accounts (guest, everyone ...).
Hi Daregre and Malcolm 127
Many thanks for taking the time to reply to my problem.
I have removed all security restrictions on the Bridge cache folder and although it's early days yet, in the short space of time I've used Bridge since, I have not received the error message (fingers crossed).
I must confess I do not understand the logic of this because, as I said in my original posting, I had been using Bridge quite happily for six months, never changed anything and this problem suddenly came out of the blue.
I must also add that with the volume of correspondence there has been on this issue, I am disappointed that Adobe seem to have been silent on the matter.
In my testing today, the problem is still there.
I checked my permissions and disk space for my caches, and that is not the problem.
Here are some clues to the folks at Adobe to where this problem might be:
Open Bridge CS4, go to a folder of 35 Canon 5D2 CR2 files, and purge the cache for the folder. Select the first thumbnail, hit the spacebar, then the plus key, and right-arrow thru the files (at 100%). After a few images, it starts to take longer for the 100% view to fully resolve. On the 9th image, it never resolves and eventually gives the 100% unavailable message. Escape out of the 100% preview and then go back to the first image to show 100% unavailable. It still shows "100% unavailable". Close Bridge, reopen, open the previously 100% unavailable image and it displays fine. So the 100% unavailable error was stored in RAM cache. If you leave Bridge open but purge the folder cache, it also resolves the 100% unavailable problem.
If you open a folder and very rapidly right-arrow thru the files at 100% preview, after about 7-10 files Bridge goes berserk, starts flickering, gives the low memory error, and dies.
Since Adobe pays people (and I'm not one of them) to fix these things, I'll sign off here.
Hopefully this will help.
Europe, Middle East and Africa