Comment 7 for bug 1815305

We perform the TagLib save() operation on a temporary copy and replace the original file only after all operations have completed successfully. This is not very SSD-friendly (...thinking about how to avoid and disable it on demand...), but the safe route.

I will add a size check of the temporary copy and the original file before starting to save the tags for an additional level of safety. But we still need to rely on the consistency and reliability of the underlying file system and that TagLib saves metadata without corrupting files.