I ran into another issue similar to my other post at UXP bug - processing just stops - #9 by ddbell.
However, while the symptoms are similar, this is a different cause. For this case, the user’s computer is stopping after the second image during a batch process for my Face Crop plugin. In this case, it is directly related to his custom workspace. I spent about an hour on his computer trying to figure out if there was any specific configuration that triggers it. I rearranged his custom workspace many different ways but it always would stop. The essentials workspace always works.
In this video, you can see the issue toggle on and off by switching the workspaces. For this user, he is running a dual monitor. Not sure if that plays a role. However, all of Photoshop is on one monitor. In the screen recording, you can see both of his monitors.
In the UXP logs, there were zero entries made for the timeframe of this video recording. I recorded this same sequence twice and rebooted between the recording. Both times there were no log entries. The only log entries that were made were during the reboot sequence.
For the other post I made where resetting the preferences fixes it, the workspace is those cases doesn’t seem to play a role. In those cases, we tried setting the workspace to essentials and resettign the workspaces and that didn’t fix it. Only resetting the preferences fixed it for the other post I made. Also, for the other tests in the other post, those were with a different plugin. Those were with EZ Team Builder. The testing in this post was with face Crop.
There is nothing different for what each image in the batch does for processing steps. The second image will run the exact same sequence as the first image. In every case, the first image runs with no issues so I don’t believe this problem is due to any of the processing steps.
I am dealing with a couple of these per day right now. The vast majority of the computers are fixed by resetting the Photoshop preferences. However, this one was unique from the rest so I thought I would post it separately. Maybe it is related to the same bug… maybe something different??? In any case, the occurrences are starting to pile up on me.