ok, even as i type this, my processes menu is telling me:
Full Version: Memory for appz
| QUOTE |
Image Name User Name CPU Mem Usage Photoshop.exe J______ 43 403,968 K |
im right in the middle of working on a 345 Mb Photoshop file, and i havent saved for about 2 hours. as you can imagine, i dont want to loose any of my work. but, upon editing a large amount of type, PS freaked out and started to freeze, and is giving me the dreaded [Not Responding] next to the app name.
Now, the Mem and CPU usage for PS is still going up and down as if it is processing, and i got an error before saying my comp had to increase the size of its Virtual Memory for the Page File Usage History.
What i want to know is, is there anyway i can hold onto my work and not force quit Photoshop? If i leave it for long enough, will it sort itself out? Can i increase the memory available to PS and the Page File History, so it will finish its process? Is there anything i can do?
yeah, sometimes BM just leaving will work. depends if the program enters and endless loop in its process, if that is the case, memory is leaking and building up. and will need to be shut down.
SOME *** SOME*** times PS 8 has recovered the file for me.
you can also check info ont he PS page file, it recommends it being oon a different drive or partiion that the system page file.
check the options of PS for the page file stats and info.
I will see about the sys PAGE file size recommenndations by Maximum PC, just have to flip through it.. but i think it will have to wait until morning.
SOME *** SOME*** times PS 8 has recovered the file for me.
you can also check info ont he PS page file, it recommends it being oon a different drive or partiion that the system page file.
check the options of PS for the page file stats and info.
I will see about the sys PAGE file size recommenndations by Maximum PC, just have to flip through it.. but i think it will have to wait until morning.
You can decrease cpu usage and memory by flatteing layers, but you should save the origanl and name it different if you are going to do so.
PS is a resource hog when it comes to projects over 100MB
PS is a resource hog when it comes to projects over 100MB
thanks for the tips guys 
in the end, PS crashed all together, and i lost my work. had to start over, but oh well
in the end, PS crashed all together, and i lost my work. had to start over, but oh well
Dang that does suck.....when I was working for Navigation 2 years ago doing a print design job, we where designing the Semi Trailer sides for the Nokian delivery trucks, well a 18 wheeler semi side is massive. The files where like 2-4gb .psd files layered.
We did them at 120dpi max and some even smaller and interpolated or whatever they call it at like 96dpi, I had a Dual G4 Mac I worked on with it and it had 1.5gb of ram in it and it took 45 minutes to save it and 45 minutes to open it before I could even work on it, days where slow and kind of tedious.
When it crashed and you lost 4 hours of work, now that sucked sometimes some filters I could not even run, I let one run all night before it finished.
We did them at 120dpi max and some even smaller and interpolated or whatever they call it at like 96dpi, I had a Dual G4 Mac I worked on with it and it had 1.5gb of ram in it and it took 45 minutes to save it and 45 minutes to open it before I could even work on it, days where slow and kind of tedious.
When it crashed and you lost 4 hours of work, now that sucked sometimes some filters I could not even run, I let one run all night before it finished.
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.