When I went to open another file, I was told it could not be done because of a lack of memory. Photoshop was using 5.6 gigs of RAM. Bridge was using another 0.5 gig.
Photoshop is set (left default setting established by Photoshop) to use scratch space on drive C which because I just started with this computer a few days ago has about 500 gigs of free contiguous space. But actually I don't to make much use of scratch space because such use would slow computer down.
Does the 64 bit version just keep taking more and more RAM without releasing any after a file is closed? I gave computer several minutes wait to see if Photoshop would release memory--nope.
Everything ran fine until that error, machine did not slow down at all.
Its annoying to have to close Photoshop because it doesn't release memory.
Are other people finding that the program fails to release memory?
Robert
What exact error did you receive, from which application?
But actually I don't to make much use of scratch space because such use
would slow computer down.
How do you know that? Photoshop determines scratch usage.
And it is not ideal to have the scratch space on the system drive.
Photoshop was not reusing memory--if it had been, it never would have taken up 5.6 gigs. My files were not enormous. Most files as raw were ca 16-17 megs. Those that I made substantial changes to and saved as psd files became 70-75 or rarely 80 megs in size. I closed each file after processing it. I think if Photoshop was properly reusing memory,it never could have swollen to 5.6 gigs.
Mylenium
What version of the Camera Raw (CR) plug-in do you have? Are you opening them into Ps as Smart Objects or just images? What camera model and format are you using?
thx,
steve
Read the following thoroughly:
<http://kb.adobe.com/selfservice/viewContent.do?externalId=kb404439&sliceId=1>
PS only releases memory on exit.
PS does not always re-uses existing allocation if a new image does not fit into allocated contigous blocks.
Example:
Open 10 125MB files -- ok, allocation is 1.5G give or take.
Close all files
Allocation remains at 1.5G -- this is how it is designed.
Now, Open a 540Meg file.
PS will allocate an additional 500 or so Meg. Memory jumps past 2.2G and thrashing starts.
There are long discussions in the beta group on this.
The momory allocation scheme was built-in to speed PS operations. But images are now so large, the the memory manager will have to be redisigned prior to the next generation of imaging, or there will be real trouble.
H
PS only releases memory on exit.
or at the request of the operating system.
H
I do see your point Hugh.
I am not sure about "or at the request of the OS".
it may or may not relinquish it depending on how it is written.
just relaying what chris cox said (recently even). if the os needs ram for another app, photoshop is supposed to honor that request. i don't work for adobe so i can't guarantee that statement, but in theory i know it is POSSIBLE that it's true! :)
Photoshop works really, really hard to reuse the memory it has (freeing and reallocating is a nasty performance hit).
Some file format plugins allocate buffers outside Photoshop's memory pool, and opening files with those plugins may thrash memory a bit. We're also working on a memory problem related to ACR.
A memory intensive app like Maya doesn't use it, nor do a lot of other memory intensive apps and they all seem to work quite well without it.
I always thought that MM in PS was a Mac thing that was put into the Windows version because the early DOS based OSes were crappy at MM, which wasn't a problem for the NT based OSes.
The memory management in Photoshop has nothing to do with specific platforms, and everything to do with performance and stability.
Most of what we do is forced by the realities of dealing with large documents, large histories, trying to keep performance reasonable, trying to guarantee results at critical times (do you really want document previews to fail randomly?), etc.
dm: .... or any other app that wants memory space. AV, who needs it?
AV, who needs it?
dumped vista and running linux now? :)
If you care to try a Beta RC to check and see if that indeed helps you're case, here's a thread:
<http://www.adobeforums.com/webx?128@@.3bc03c04.59b7a792>
and here's where to find it:
<http://labs.adobe.com/wiki/index.php/Camera_Raw_5.3>
regards,
steve