There is strange bug I’ve been dealing with that is affecting 3 of my different batch processing plugins. I’m pretty sure this is a bug in Photoshop itself. I’m hoping to get help from an Adobe developer on this one.
This has been reported to me by at least 50 people. There are probably many more affected. However, I have a work-around which I posted on my facebook tech support group so a lot of the users already know what to do in case it happens so there are a lot who haven’t reported it I’m sure.
This has been difficult to troubleshoot because I can’t replicate it on my systems, although I did have this issue at one time a few months ago and did a little testing at that time.
This issue is on both Windows and Mac and affects all Photoshop versions in including the latest public release 22.2.0. I don’t know if the pre-releases are affected because I can’t even replicate the issue on my systems. This is being seen on the users systems so 22.2.0 is as high of version that I know about.
Here are details about the issue…
There is no error. The UXP processing just stops. All 3 plugins I am seeing this on are batch processing systems that open images one at a time, do some processing, then close and open the next image. No of my other non-batch plugins have had this issue.
The first image in the batch processing always runs without an issue. It is almost always the second image when it stops. A couple of people have reported it will run 3 or 4 images before stopping but I haven’t verified that myself. Any verified occurrences have always been the second image where it stops and always in the same place in the processing. There seems to be a common stopping point. It will perform the first batchPlay on the second image in the batch and then stops when the next batch play tries to run. If there is other code between the batchPlay steps like setting variables or something, those steps process fine.
I first thought this had to do with the batchPlay step to create a new history state because all 3 plugins had that step in there and it seemed to be where it stopped. However, I then made a new version to test that didn’t use history states at all and had a user test it. It then stopped after the next batchPlay which was just a single descriptor to select the bottom layer.
This issue is linked somehow to the Photoshop preferences, but I don’t think an actual preference setting itself. This issue is always resolved after the users resets the Photoshop preferences and restarts Photoshop. In almost all cases the issue never comes back after the user resets the preferences. However, there have been 2 users I know of that have had the same issue come back and resetting the preferences fixes the issue every time… at least temporarily.
Even though resetting the preferences fixes it, I don’t think there is an actual preference setting causing it. It happened a couple months back on my Mac and I know for certain I was running default preference settings on that computer. Resetting the preferences fixed it and it hasn’t come back since on my Mac. One user on a Windows system recently has had to reset there preferences multiple times. They claim that they didn’t make any preferences changes between resetting and the next time it failed a few days later.
My next troubleshooting steps planned…
What I would like to do the next time a user reports this is have the user save the preference .psp files before and after resetting and also collect any logs to send to Adobe. Would this be a good plan? If so, what are the specific files and logs that would be useful o help troubleshoot this?