CS2 seems to pause regularly...and I finally pinned down that it is when rendering the image after panning. At first I thought it was only on larger files with many layers but I noticed it this morning with a new, single layer, 16bit PSD (only about 50mb).
- If I use the mouse and scrollbars the image pans fine.
- If I use the spacebar for the hand tool it is so slow as to be unusable.
- If I create a selection and try and 'nudge it' with the cursor keys it is also unusable.
I have CS2 (9.0.2) running on XP sp2, 4gb (32bit XP, so shows 3.25), pentium dual core, ATI 1800 XT (512mb) g-card
CS2 is running at about 700mb, nothing else large running. I do notice that I go to 50% CPU for the couple of seconds that I wait for the screen to catch up - I thought CS2 could take advantage of both cores?
I do not remember this problem a few months ago but I can't think what I have changed to cause the issue or when it started.
Any ideas on where I should look? I have an IT professional services background so feel free to go technical on me
How frustrating. Have you tried updating/reinstalling your display driver? Failing that I might try reinstalling CS2 also.
I wonder if other graphics applications would also exhibit this behavior. Perhaps download one of the trial versions. If so, it would point more toward the display driver or hardware. Good luck. Please let us know if you solve it.
Thanks David - I have checked in Paint Shop Pro X and Gimp but no problems - I even opened loads of images, one after the other, and fine in both packages. If I leave CS2 running but without any images open it seems to return to normal. I am now wondering if it is to do with the way it cleans up it's cache?
Very possibly. I have to shut it down occasionally if I'm running a lot of images through it. I'm a programmer (retired) and have always been appalled at PS's memory management.
Mark, I had a similar problem a few months ago and found an answer on dpreview where you held down 4 different keys (something like ctrl-alt-shift and ?) while starting up PS, and it cleaned out some corrupted initialization settings. It fixed things right up. I'll try to find the key stroke and will post it if I do.
That's it, Mark. I'm gonna write it down this time. I hope it works for you.
Posted by Mark Wilson on July 11, 2007 at 10:19 AM
Unfortuneatly deleting preferences hasn't solved anything...if I load a larger file with multiple, masked layers I get the symptoms above. If I close the file and leave CS2 running, open a single layer file I get the same problem. If I close CS2 and then restart with the small file, everything is fine. If I open and close a number of files in one session (creating web-images from master files for example) the same thing starts to happen...
...so I think it is a memory management issue. Opening and closing several files, the process memeory usage just grows. If the CS2 process gets above 600mb the problem occurs (windows reports 1.8 gb physical memory still available - so shouldn't be a swap issue). If I leave CS2 idle for an unknown period of time, a clean-up process seems to run and things improve again.
Has anybody got any ideas what I can tweek in the CS2 settings to help it clean-up a little faster?
Discussion
7 replies- If I use the mouse and scrollbars the image pans fine.
- If I use the spacebar for the hand tool it is so slow as to be unusable.
- If I create a selection and try and 'nudge it' with the cursor keys it is also unusable.
I have CS2 (9.0.2) running on XP sp2, 4gb (32bit XP, so shows 3.25), pentium dual core, ATI 1800 XT (512mb) g-card
CS2 is running at about 700mb, nothing else large running. I do notice that I go to 50% CPU for the couple of seconds that I wait for the screen to catch up - I thought CS2 could take advantage of both cores?
I do not remember this problem a few months ago but I can't think what I have changed to cause the issue or when it started.
Any ideas on where I should look? I have an IT professional services background so feel free to go technical on me
I wonder if other graphics applications would also exhibit this behavior. Perhaps download one of the trial versions. If so, it would point more toward the display driver or hardware. Good luck. Please let us know if you solve it.
...so I think it is a memory management issue. Opening and closing several files, the process memeory usage just grows. If the CS2 process gets above 600mb the problem occurs (windows reports 1.8 gb physical memory still available - so shouldn't be a swap issue). If I leave CS2 idle for an unknown period of time, a clean-up process seems to run and things improve again.
Has anybody got any ideas what I can tweek in the CS2 settings to help it clean-up a little faster?