No clue, except if you can do in chunks, say 10% at a time, maybe you can get 9X% (or even 100%), and if doable in chunks, you might ultimately isolate problem photos.. (and be able to file a re-producible bug report so Adobe can fix).
Note: it's not uncommon for plugins to croak when doing multi-thousand photo operations, but the pre-symptom of failure is usually ram exhaustion (out of real memory -> using virtual memory..) - dunno if you are seeing such behavior (?).
FWIW: the solution for such plugins is often to break into chunks internally, and do each chunk individually, freeing memory between chunks.. - dunno if Adobe has gone to such trouble in this plugin, maybe not..
Maybe somebody else has more specific experience and can help more..
Processing in chunks didn't work - it always stops at the same percentage. Memory is no issue, didn't increase during operations and no swapping could be monitored!
Sorry you are having trouble with the plugin. The plugin will create the result you desire, and with a lot less effort. See this thread.
But since you are having trouble, have you deleted the problem image and emptied the trash? Does the file use foreign character sets?
And yes, although they did create it, Adobe hasn't been very helpful with the plugin. Makes me wonder about the kind of support we'll receive moving forward. Forums don't seem active either.
We are working on an update that should resolve these steps at x%. Stay tuned. Sorry for the trouble so far.
Thank you Pete. Another forum poster says Adobe has been hard at work. I stand corrected.
Pete, any estimate on timing of the update? I've tried three times and it always stops at 64%.