Looks like your prefs file might have become corrupted. Try trashng it (as detailed in the FAQs). Chances are that’ll get PS using its correct allocation.
Chris.
Thanks Chris. This worked for one session, but that’s it. It is continuing to do the same thing again.
David.
That message can come up incorrectly if a pointer is NULL when it shouldn’t be. That normally happens when the install or OS is corrupted (missing dialogs, failure to initialize a dialog, etc.).
The Windows Task manager is indicating that Photoshop is taking up over 1.5G AND PS is very sluggish.
1.5 Gig is normal.
Sluggish is not normal.
In my opinion it has nothing to do with the ammount of RAM. It’s a bug. The very same thing happens to me when working with 32×32 icon images so it can’t be RAM’s fault.
There is only one common thing that I found in all the situations when this message apeared. I have both Illustrator and Photoshop opened and I copy one vector object (or a group) from Illustrator. I paste it in Photoshop as smart object or pixels (doesn’t matter). After a few operations like changing the contrast or applying some filters here comes the message. Almost every time.
Somebody help us please.
This worked for one session, but that’s it. It is continuing to do the same thing again.
CT: Are you closing Photoshop down correctly before switching off?
I have both Illustrator and Photoshop opened
MP: How much memory do you have allocated to Photoshop? Have you tried trashing the prefs? Have you got plenty of defragmented free space on your scratch disk?
It’s always worth doing a search for .tmp files and deleting them all.
Best of luck with it, both.
Chris.
A 32×32 pixels image in Photoshop can’t have more than few kb, even if it has many layers. I tell you again, it can’t be a RAM or allocated memory problem. I have enough RAM and enough percent of it allocated to Photoshop, enough disk space and enough everything.
_____________________
It can be if the memory allocated to PS is too high. The there is nothing left for the OS.
Take PS allocated memory down to see what happens.
Rob
Ok. I have a total ammount of memory of 512 MB. 438 MB are available usualy. 77% from these are allocated to Photoshop (meaning 337 MB). I tried the default percent, lower and higher percents and still the same error.
I remind you that I am NOT working with big files, they hardly exced 50KB. ___________________________
I have a total amount of memory of 512 MB. 438 MB are available usualy. 77% from these are allocated to Photoshop (meaning 337 MB).
CS2 can work with 512MB of RAM – but it struggles. 1GB it is comfortable. 2GB it runs really smooth.
The thing to remember is that if Photoshop is hogging too much memory, the OS, most of your plug-ins and filters, Bridge (if you’re on CS2) and even the "Save" function, will be starved of system resources as they all work outside of Photoshop’s allocated memory. Not to mention the fact you have Illustrator trying to run at the same time!
I get best overall performance at the 55% default setting and I have 2GB or RAM. With your settings you’ve only left 100MB of RAM for all these other things to fight over.
I am NOT working with big files, they hardly exceed 50KB.
Photoshop opens a scratch file for even a tiny image, so make sure you have several GB of free defragmented space on your scratch disk. I’ve just opened a new 200 pixel square image (100K) and the scratch file is 85MB. That is how Photoshop works – constantly writing stuff back and forth to scratch to keep RAM available for memory-intensive procedures.
You also need lots of free space on your system disk and have Windows paging file set to min=max=4GB
Best advice: Go buy more RAM. In the meantime close down everything else whilst running Photoshop and drop its memory allocation to below 50%.
Chris.
check to see if you REALLY erased the scratch files when Photoshop closed.
Hey, I tried all your advices and thank you for all. But nothing changed for better. Still the same error. I still don’t think this is a machine performance problem.
Just tell me how or where to send you a jpeg capture of my desktop to prove you this.
——————–
Marius,
Did you read mesage #3?
Yeah, I did Len. And that’s why I stick whith it. Because everybody else insist on machine performance issues. Am I right or not?
🙂
