Image Processor bug causes PS to crash (CS5, 12.0.4, Win7x64) -

Question

Hi,
I'm trying to process 64 RAW files using Image Processor, and I noticed that Photoshop (x64, I don't have the 32-bit version installed) never closes any of the files after it has processed them. This causes the RAM to fill, and eventually Photoshop to crash. I tried both via Bridge (Tools --> Photoshop --> Image Processor), and Photoshop itself. I have a new system with 8GB RAM, and when I start up Image Processor, Task Manager tells me PS eats away 6.5-7GB of it during the first minute. Shortly after PS crashes.
My updates are up-to-date according to the update manager. I haven't had this problem ever before, so the cause must be the 12.0.4 update (or the one before it). Is there a workaround or an update on the way? Maybe this is a known bug. I found out that people have experienced the same behaviour with CS4.
Kind regards,
Kimmo

Answer 1

Sorry for the delay in response; the Adobe server for logging in was down for hours.
The reason I'm on the latest drivers is that I made a clean install of Windows 7 a couple of days back.
Regarding the Intel driver I mentioned I downloaded: I had to go another route; the Intel driver "was not validated for this system", so I had to get the latest driver from the manufacturer of the computer -- which kind of sucks, to be honest. Well, anyways, the driver version from the manufacturer is the same I had from Windows Update (i.e. not the latest possible), but I went and installed it anyway -- thinking that maybe it's been "customized" somehow...
Unfortunately it brought no change. Action B still accumulates files while others do not.
I should clarify that the reason why the "Wood Frame" kept accumulating files in the PS main window was that it never finished the process. I tried it to run on pictures that were larger than what it was designed for and thus it stopped mid-process and left the window open.
(BTW: I'm talking about windows and tabs interchangeably here)
"Action B", as I've called it in this thread, does generate a final, processed JPEG, but apparently it doesn't return a confirmation of it finishing to the Image Processor. Without Image Processor knowing that the script finished successfully it leaves the file open.
I see that in File --> Automate --> Batch it is possible to have the process "Save and Close" each file it processes. Maybe it would be beneficial to have a similar function for Image Processor. And not only "just in case" -- the user might actually want to leave all the files open, who knows, but in situations like these a forced closing of a file -- be it finished or not -- would be nice.
I would also like to point out to other people reading this thread that, while this problem can be fixed by simply remaking the troublesome action, I feel finding the cause for it would benefit a lot of people too. Maybe the action was corrupted somehow, maybe PS 12.0.4. has a bug that makes my "Action B" from 11/2011 incompatible -- would be nice to know, huh?