I could not replicate getting it to corrupt another file. It might have been a one time fluke, or a specific use case that I just have not run into yet again. A possible solution is to make a copy backup of the image before adding a tag, then checking to see if the image is corrupt after adding the tag and either restoring the backup or deleting it. Both windows and the apps logs show when an image is corrupted.
I could not replicate getting it to corrupt another file. It might have been a one time fluke, or a specific use case that I just have not run into yet again. A possible solution is to make a copy backup of the image before adding a tag, then checking to see if the image is corrupt after adding the tag and either restoring the backup or deleting it. Both windows and the apps logs show when an image is corrupted.