Potential Memory Leak with change emulation

We have a process which is looping through PDF files and adding them to metadata, when the change emulation plugin was inside this loop, we were getting through exactly 1059 files and the loop was freezing, after removing the emulation change and placing it outside the branch, the problem seems to have been solved.

Hi.

If you could give us more details for us to be able to reproduce the problem, or even better open a case with our Support department, we’d be very much interested in checking this out and putting this on our todo list.