Bridge CS4 - low on memory error

Still something not OK. It seems to me as if there are two different beasts in one skin. There are still some RAW files which - when previewed via Slide Show are still unavailable at 100% view (they were adjusted with ACR 5.2). Bridge displays them with low resolution - it just shows "loading" for ever and finally displays "100% unavailable". Switching directly to ACR with "R" key displays the file with no problems. No matter if you purge the cache, or switch to software rendering. Only thing that helped was to rebuild the associated XMP file (either delete or open the file in ACR change a bit of something and resave). It seems to me that ACR 5.2 - with its unpredictable behaviour under heavy load - corrupted some XMPs which finally resulted into situation that Bridge cannot display them correctly (however ACR has no problem with them).

Is it possible that Bridge and ACR use separate rendering engines for displaying files? Or they interpretate the XMPs with different algorithms?

Hmm after installing ACR 5.3 seems to be something good happened. Not testing it much exhaustively but the adjustment brush is less "jerky". I applied 6 graduated filters on a PEF file, 4 adjustment brushes to differnet areas - memory allocation for Bridge increased to 1 GB but after pressing "Done" button the memory was immediatelly released to 240MB - so far so good.

Ron: Surely just not using the adjustment tool or the gradient tool in ACR 5.2 will avoid the memory leak problem? also, have you noticed that ACR 5.3RC has been published? you might want to try that.

Anthony.

Than you Curt and Don for your help.
I am now opening Bridge CS4 and collating the images for editing.I then open the NEF images with PS cs3 running in the background. This opens camera raw 4.6 (which thankfully does not contain the adjustment brush nor the gradient) as it would appear that those 2 beasties caused my problem in the first place. I then proceed with any further editing in CS3....I will follow this forum to see whether Adobe gets around to fixing the problems in ACR5.2 Thanks once again.

The Raw image problem is an ACR 5 and 5.2) memory leak problem. Your other problem is, as suggested, a video card problem. Going back to CS3, which does not use Open GL, will take care of the video card problem, but you should be sure to upgrade to the latest nvidia drivers, if you have not already done so, Realize, as well, that your 4 gigs of ram will not be fully utilized on an XP 32bit system.

Also, going back to Bridge 2.1 will get you around the memory leak until it is fixed by Adobe--the word is that will happen soon for ACR 5.2.

Thank you Curt,
Using "software rendering" seems to have fixed the problem with the film strip and preview window problem. The problem with the non focusing loupe on TIFF images remains as does the bridge memory problem.
I am tempted to revert to CS3.. never had a problem with that.
Thank you for your help

There may be more than one problem working at the same time.

Regarding the filmstrip mode problem, that usually is a video card thing. Make sure you have the latest drivers. Clicking on "use software rendering" in advanced preferences can also help.

further to my post of yesterday where I referred to the problem with the loupe in bridge further problems have arisen. If whilst in filmstrip I use the space bar to enlarge the image and then tap the space bar to return the preview to the original size I am unable to view another image in the film strip by clicking on it .. the preview screen remains blank until I slightly adjust the bar which divides the film strip from the preview panel.
Since yesterdays post I have gone to bridges cache and found files called 256, 1024,data and full. I have manually deleted those files but the problem has not gone away.I have also gone to tools and purged the cache from the relevant folder.
The loupe problem does not occur with NEF (raw) images but only with
TIFF images.
I am also getting the message that Bridge is running low on memory and needs to be re started.
I am not batch processing . I have about 150 images in the open folder and I am working on one image at a time.
I would appreciate any help

I have just installed CS4 ( I am also running cs3) on windows Xp.
I have 4 ram and a nvidia geo force 9800gtx card. I have been having little quirky problems with cs4 ( cs3 continued to work perfectly )
Today a problem has appeared. I opened a raw image and edited it using the adjustment brush , the gradient and converted to black and white. It was after this that the problems occured. A shrt while after opening the file in photoshop cs4 I noticed that the efficiency rating had dropped to 35% ! I closed the file and reopened it in CS3 and the efficiency returned to 100%. I then noticed in Bridge that when I used the loupe on that image the loupe could not focus and a message appeared below the preview picture that"100% not available"
Interstingly the loupe had no problem with NEF images in the same folder. I then went to tools / cache and purged the cache for that folder ... The loupe worked but only for a short while before the same message appeared and the loupe would not focus ...Any thought as to how I can fix this? I would be very grateful fotr any help.

They are undoubtedly well aware of the memory issues. Both Lightroom and ACR share the same basic engine and both have the memory problem--it has been widely reported and they have acknowledged the memory leak.

The problem is far more crippling on computers with smaller amounts of memory, of course. It makes using the adjustment brush, the grad tool, either LR or ACR, and other file intensive operations, like large exports from LR or batching from ACR, virtually impossible on my older P4 2.4 with two gigs of ram. It is not a problem for me on my Intel 9550 quad, with 8 gigs of ram. However, I seldom ever use the adjustment brush anyway, not because of the leak, but because it is a very primitive tool, comparatively speaking, for local corrections.

Ironically, this memory leak bug was introduced in their attempt to speed up the adjustment brush. Now it is faster and smoother--and works fine, that is if you use it very sparingly, or constantly reboot to get your memory back. I suspect a fix will be released soon--let's hope it doesn't come with another new bug to deal with.