#11 Multiple atomicparsleys in parallel interfere with each other

[Kenneth Herron]

Multiple AtomicParsley jobs in parallel can interfere with each other. After an AP process exits, kmttg detects the temporary files from the other AP instances and deletes them. This causes errors in the other AP jobs, resulting in the loss of the files being processed by AP.

1. Open the "files" tab and add some files to it (The files may have to be in the same directory).
2. Select a few of the files and click "Run AtomicParsley".
3. KMTTG queues up an AP job for each file and launches them in parallel.
4. When the first AP process finishes, kmttg reports "Found temporary file left over from AtomicParsley job" and "Removing foo-temp-57682.mp4"
5. The instance of AP which was actually writing foo-temp-57682.mp4 eventually exits with an error, which kmttg also logs.

The files being tagged by the failed AP instances end up being deleted--not sure if by kmttg or AP--so this leads to data loss.

Workaround is to run AtomicParsley one at a time.

[Kenneth Herron]

Sorry, meant to add I'm running v1p0s. I first noticed this a couple of revisions back.

[Kevin Moye]

OK, I've checked in code for next release that will only allow 1 AtomicParsley job at a time in FILES mode.
Thanks for reporting this.