Temporary files (TMPxxxx.tmp) not deleted after Mp3tag "Cannot write file" error message is dismissed

[ryerman]

I found this behaviour when trying to edit the M4A file found here.

It seems that Mp3tag creates a temporary file of an M4A file being edited.
Maybe that happens all the time, for all file types.

When Mp3tag cannot open a file for editing, an error message is displayed that asks if I want to retry.

After clicking "No", the program returns to the "Ready" state.
However, a tempory file (eg. TMPB239.tmp) remains, beside the file being edited.

For me, that is undesired behaviour.
I expected the temporary file to be deleted.
Maybe it is a bug.

Windows 10 Home (64 bit), Mp3tag v3.18f (32 bit)

[ohrenkino]

Here is a thread that claims that the bug has been fixed:

[F] Leftover .tmp file if media file could not be opened for writing

If mp3tag for some reason fails do save tag data to a media file, a temporary copy of the media file is left and not deleted. To reproduce: run mp3tag in a given directory open a media file in this directory with a second application, f.e. winamp or ultraedit change the tag data of the file when attempting to save the tag data, a modal dialog will popup informing you that the file cannot be opened for writing choose ok and open the directory in the browser -> You'll find an additional tmp fi…

So, perhaps something new ...

[Florian]

I've reproduced it locally and have just fixed it with Mp3tag v3.25a.

Thank you for reporting (and for patience)!