When I close a large document Photoshop does not release the memory. If I open another document the program is slow and not resposive. If I close out of Photoshop and restart it then load the other document it is quick and responsive again.
And that is the correct behavior -- Photoshop reuses the image memory that it allocates (up to the limit you set in preferences).
If it didn't do that, things would run much slower.
Normally there is no need to quit and restart Photoshop -- all the memory just gets recycled.
If the program is slow and unresponsive, there is something else going on.
...something to cause the memory not to be recycled?
The file I loaded after closing the initial file was less than half the size of the initial file.
Could it have something to do with Norton Internet Security? maybe the Performance Moninitoring? I went into Norton Internet Security Settings>General and turned Performace Monitoring Off. Hopefully this will fix it.
I don't remember having this issue before installing Norton Internet Security
Norton should not interfere with Photoshop. If you do find it causes problems, then we need to get some details so we can follow up with Norton.
And we have not seen an instance where Photoshop was not reusing memory.
The only things that can make Photoshop throw memory away are the OS, and some plugins.
After that Photoshop will have to reallocate (slowly) the memory it needs.
A bit late to the party here but this issue is still live and I can't find anything else on the forum similar to it (apologies if there is).
Photoshop does not seem to re-use memory it just keep allocating new right up to the limit before the prog crashes (same applies to Fireworks) so any batch/script processing of more than a handful of files is impossible.
I am Photoshop via Creative Cloud (so I am always updated to your latest release), Windows 7 64k with 8Mb memory and am using Norton Intenet Security 18.104.22.168 which is updated daily.
Photoshop definitely does reuse memory, and we haven't seen other users with problems outside of this topic (which was caused by some bug in Norton).
But you could have a third party plugin, or even a Flash Panel that leaks memory that badly.
Or Norton could have reintroduced their bug.