I have searched here and elsewhere on the internet but found little help for my problem (only one thread here (2009/01/22) and it didn't mention anything I hadn't tried). So if I missed a thread, my appologies.
I am trying to stitch a 24 image pano together and I keep getting "The application ran out of virtual memory. Please close some windows to free memory". The thing is that PS is the only app I have open! This is definitely the largest pano I have ever tried.
I have 4GB of RAM, two internal hard drives with the app on one drive (C) and the scratch disk on the other physical drive (G; this drive has 115GB free). Preferences -> performance tells me that I have 1707MB of available RAM (I'm guessing that CS3 PS can only access 2GB), and I have tried giving it from 70% all the way up to 90% (1536MB). Control Panel -> Advanced -> Performance -> Advanced, Virtual Memory paging file for C is max of 5120MB while G on the other physical drive has an additional max of 7168MB. But total paging file size on all drives is currently only 4603MB! I saw something on the web that said to disable Version Cue, which I did but it didn't help.
I tried to merge all 24 pictures, but it didn't work. I rebooted and tried 12 at one time, with the idea of flattening the layers and saving it, doing the same with the other 12 and then merging the two resultant pictures. But I got the same error with 12 pictures, so I rebooted and tried 4 and got the same error again!
The files are 11MB to 15MB, with most being 12 to 13. The source files are Canon CR2. I ran Task Manager with Virtual Memory Sizes column added. What I saw was 1.66GB of real memory used along with 1.64GB of virtual. So while real memory is being well utilized, my virtual memory is not. The Doc Size was 57.7MB for each and the Scratch Disk value was 151.5M/1.5G. Efficiency was 100%. Is this a problem with Photoshop CS3? Almost forgot to mention; version is 10.0.1.
If I merge two pictures, flatten, merge another two pictures, flatten and then attempt to merge the resultant two pictures and so on, am I going to run into the same VM problem, just a little later in the work flow?
Any suggestions? BTW, I have seen some suggestions to reduce the source file sizes, but then what is the point of shooting multiple images? Might as well just shoot one high res image and go with that.
It's counterintuitive, and kind of a longshot, but try reducing the memory you allow Photoshop to, say, 50%.
Not every plugin allocates memory from the pool allotted to Photoshop, though to the best of my knowledge Photomerge does. Whether it DID in CS3 I don't quite recall. But it's an easy test to make.
Make sure you restart Photoshop after making any changes to Photoshop's memory setting.
Virtual Memory is an operating-system configurable thing. If you have a fixed-sized virtual-page-file or a relatively low maximum then you've run out of that, and you can just go in and make it larger, unless you've also run out of space on your hard-drive, then you can add a paging file to another hard-drive if you have one.
In Vista I can get to the Paging File configuration by going through these steps:
My Computer -> Right-click -> Properties -> Advanced Re: PS CS3 - running out of virtual memory! -> Performance Re: PS CS3 - running out of virtual memory! -> Advanced Re: PS CS3 - running out of virtual memory! -> Virtual Memory Re: PS CS3 - running out of virtual memory!
If you have plenty of free space on your hard-drives just set it to System Managed Size. If you are running short on some drives, then allocate a paging file for each of your fast internal drives and see if it is enough.
I would suspect it is misleading you and in fact wants more physical memory. If so, you have no way of fixing that otehr than getting a 64bit machine with plenty of RAM and trying it again with the 64bit version of PS. Might work, might not. All this stitching and merging stuff in PS seems to be rather fragile, no matter what...
"The application ran out of virtual memory. Please close some windows to free memory"
That's not a Photoshop error message.
It sounds like your system disk could be low on space, or your Windows paging file is set to too low a limit.
Chris, I still do not understand WHY this is happening. Even when I try 4 files that when uncompressed add up to only 231MB, it fails. This makes no sense. PS is reporting it can use 1.5GB of memory. I don't see why this would even be bothering with VM. It should be an in-memory operation. I also have a huge amount of paging space (about 12GB in total). This seems like overkill for the task at hand rather than being insufficient!
Is the photomerge not actually using real memory from that which has been covered out for PS from within PS. I started at 70% and increase it to 90%. I'm think I should try going the other way and reduce it to 40% or 50%, leaving more for Photomerge to use if this is the case.
Something about your system configuration is the cause -- but we don't know your complete system configuration.
EVERY bit of RAM allocated is also backed up by the OS VM.
So your paging file has to be at least as large as your RAM, preferably larger.
(The same goes for Photoshop's scratch -- it always has to allocate space on the disk for everything that is in memory)
It sounds like either your OS volume is full, or your paging limits are set too low for how you are using your system (other apps might also be using Gigs of space).
Checking the VM allocated in Task Manager would tell whether it is running out. If the 12GB of VM you have allocated is spread across multiple drives, then one of them running out might cause the error, although I'd expect you'd also get a low-disk warning message around the same time as the other warning.