I keep on getting the message "Could not save ‘XXXX.jpg’ because there is not enough memory (RAM). Try saving without optimization or as a baseline JPEG."
My macpro has 8GB of RAM, of which 3gb is listed as Free in the activity monitor, and the maximum amount is allocated to Photoshop CS3 in its preferences.
Hopefully you have restarted the box, not just PS. Also, how are your hard drives set up, how full and how is scratch assigned? What Mac, OS version, app version, etc. is also necessary info.
I think this is missing the point slightly though – the real issue is that PS is having a problem because it thinks it has run out of memory, when in actual fact its has 3gb allocated to it, and the system has 2.3gb free
Back on topic, a Google search on the same error message will reveal others like you. Photoshop is simply limited to how large an image can be to be baseline optimized. There is a bit more work that needs to be done by the processor to make an optimized JPG. Whether it is a failing or an intentionally programmed limitation, Photoshop is not going to perform baseline optimized compression on huge images. It does not matter how much RAM you throw at it. (We’re assuming you are using a large image even though you never mentioned the pixel dimensions).
I don’t know how to save as an optimised baseline, or how to save not as one
It seems you are unaware of the differences between baseline standard and baseline optimized so why are you so set on using the one compression method that is giving you problems? Do you absolutely need baseline optimized?
Not really. What you have done in preferences is set the MAXIMUM percentage of available memory at any given instant that Photoshop is ALLOWED to use, and that happened to be 3GB at the time you checked. It’s a percentage of available memory AFTER the OS and any other running applications have taken whatever memory they need, and that changes constantly.
It doesn’t mean that ANY memory has been allocated for Photoshop’s exclusive use. So in fact Photoshop may be using less.
With 8GB of RAM, you shouldn’t be having memory issues, unless you have defective, mismatched or improperly seated RAM.
Also, the message may be bogus. You could be running into scratch disk issues and that may confuse Photoshop. Make sure you have designated a separate, dedicated internal HD as your PRIMARY scratch disk, not your boot drive, and that you have plenty of unfragmented drive space on that. I keep a dedicated 160GB internal drive as my primary scratch disk, and I have never run into any RAM issues even though my (older) machine is maxed out at 2GB of RAM.
I found it is not bogus. I was able to recreate it by making an abnormally large image and then trying to save with baseline optimized JPG compression. I got the same error message described.
If dc is working with a smaller web image (say of less than a thousand pixels in width) and is still getting this error, then there would be cause for concern about system setup and maintenance.
Jim [#13] …
Actually, Allen on post #1 first wondered about the size but we have all been in the dark on that.
On today’s test, I failed on an image that was 10,000 x 7625 pixels. Scaling down to 9000 x 6863 was successful with the baseline optimized compression. This was on a white/blank/noiseless image with no layers.
I’ve noticed this problem on various releases of Photoshop on various systems/configurations. YMMV.
I don’t know if this is tied to the system specs or if Photoshop has a hard limit on how large it can save a baseline optimized JPG image.
no it’s CS3, thought you needed a more specific version than that.
Well in the instance of CS2 or CS3 specific version is not necessary as the difference is native to intel and running in Rosetta (emulation) which will give you some grief
Is it happening on standard baseline images? For what reason do you need ‘optimized’? Are you familiar with the differences between these type of JPG compressions?
sorry, I don’t know how to save as an optimised baseline, or how to save not as one
We get the impression that it does not matter what type of JPG you want to save. So why not save as a standard JPG?
you are correct in your assumptions. My concern is more the fact that when this error come sup, it is after the whole of photoshop has started running very slowly, something which only a restart of the machine fixes. For this reason, I assume that PS really is somehow running short of memory, which given the circumstances I am sure you would agree is not normal. I didn’t pay this much for a machine and software to have it running this slow and for it to need rebooting!
Certainly you can refresh Photoshop preferences (see forum FAQ) and run an app like Onyx < http://www.apple.com/downloads/macosx/system_disk_utilities/ onyx.html> to clean up the system but if basic maintenance does not help, the immediate solution, as noted in the error message, seems to be your best option.
…it is after the whole of photoshop has started running very slowly, something which only a restart of the machine fixes. …I didn’t pay this much for a machine and software to have it running this slow and for it to need rebooting!
Clearly this is atypical PSCS3/Mac Pro behavior. There is a problem with individual setup. Try removing all but System fonts and operating in a new user mode. Please provide drives info as requested, not just scratch info.
Hi, I see in message #22 that David mentions adjusting the memory allocation DOWN to 90%. (At least, I assume the allocation he’s talking about is RAM.) Isn’t that still a very high figure? MB
David also said he has 8 GB of RAM. With that much RAM you can safely allow Photoshop to use 95% or even more of available memory. Photoshop will not use any more than the approximate 3 GB it can use in any event.
Remember it is NOT a memory allocation, you’re simply allowing Photoshop to use up to a certain percentage of the memory that is available at any given time, you’re NOT setting aside any amount of RAM for Photoshop, merely setting a limit as to what available memory Photoshop can grab at any given moment after the OS and any other running applications and processes have taken what they need. The figure changes continuously.