First....This thread is not 100% my stuff.
But ..... you say nothing about preferences of PS .... in EDIT -menu ..... PREFERENCES .... PERFORMANCE..... >>>> memory usage ????
Is that something to look at ?
In the past, I have found that some keyboard controls don't work until you've completed a settings change. For example, if you change something like Exposure, you'll notice that its value is highlighted. This highlight disappears when you press Enter. I've noticed that some zoom keyboard shotcuts will not work until these highlights are gone, so I get into the habit of pressing Enter after making an adjustment. It's second nature now, and I'd forgotten all about it, until I read this post.
One possibility: This type of problem sometimes can result from a graphics card driver. What card? Are you using the latest driver?
I'm running an ATI Radeon HD 4870 and my Catalyst drivers are up to date as of last week.
My PS prefs are set to give 50% of RAM for photoshop, and i've tried 60% and 70%. Too much might not leave enough for ACR, too little would be bad too.
If I cleanly boot and start up Bridge and PS and open a raw file into ACR, I can do anything. But after working with it for a while (sometimes not very long, sometimes a good number of operations) there starts to be a lot of trouble with resizing. When I first open everything I can be in the middle of an adjustment (this is a response to two posts above) and the keyboard zoom shortcuts work fine. So i know it's not just the keyboard shortcuts. Also, when the problem occurs later on (maybe with fuller memory buffers, i don't know) it's not just the shortcuts that don't work, sometimes I can't use the zoom tool or the zoom setting at the lower left corner properly either.
So I'm kind of suspecting memory leaks in the programming. In any case I'm sure this will not be an issue when I go 64-bit and get enough RAM in a few days here. But meanwhile it's a pain because it should work fine as long as I'm over the minimum system requirements, which I am with 4Gb. If it runs out it should just use more hard drive... I would understand if it just took 30 seconds to re-zoom. But that's not it; it's refusing to zoom at all when this problem occurs. I can wait as long as I want and ACR does not honor the zoom command.
It's similar to the other issue I just posted, where ACR refuses to save my raw files to any format sometimes (even to the smallest size JPEG it offers, like a 1Mb file) but is perfectly willing to open them in Photoshop where I can save them instead.
Should I be making a bug report?
I corrected a problem as a result of a different memory-related message thread, and it looks like it probably solved this one too.
I had an ACR cache folder set up on a drive with plenty of space, but I had forgotten to give it an actual cache size limit. It was at the default 1.0Gb and that is far too small! So I gave it 20Gb and everything seems to be working properly.
Still sort of a bug ... if the program is going to be unable to honor the user's command to resize/zoom the display, it should really say so, rather than just become unresponsive. But I understand that sometimes programming for speed optimization can be antagonistic to including every possible catch for stupid error conditions that the user should not have caused.
Thanks for the ideas!
Solved -- just needed to set a better cache size limit in preferences. I had set up a cache folder with lots of room but I had neglected to tell PS/ACR to use more of that room.
Will the problem return when the 20FB is full, where it is only working, now, because it's not full, yet, because you've just recently increased the limit, or is it already full and still working ok?