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

**URL:** https://community.mp3tag.de/t/f-leftover-tmp-file-if-media-file-could-not-be-opened-for-writing/12001
**Category:** Fixed Bugs
**Tags:** bug-fixed
**Created:** [May 12, 2011, 5:02am UTC](https://community.mp3tag.de/t/f-leftover-tmp-file-if-media-file-could-not-be-opened-for-writing/12001 "2011-05-12T05:02:22Z")
**Posts on this page:** 1
**Showing post:** 4

<div class="post-metadata">

### Author: ![edrikk](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/e/c37758/32.png) [@edrikk](https://community.mp3tag.de/u/edrikk)
#### Post date: [May 13, 2011, 9:55pm UTC](https://community.mp3tag.de/t/f-leftover-tmp-file-if-media-file-could-not-be-opened-for-writing/12001/4 "2011-05-13T21:55:25Z")

</div>

> [@anon40688970](#):
>
> -\> You'll find an additional tmp file in the directory which must be deleted manually. Otherwise it will stay there forever.
> 
> Do you think it is ok to waste space on the user's hard disk without any reason?
> 
> If mp3tag is able to diagnose the problem and show a dialog it should also be able to delete the self-created tmp file afterwards.

Yes, this is true. The .tmp file is left behind... This is especially an issue if the file happens to be a 2GB to 4GB .mp4 file...

---

_[View the full topic](https://community.mp3tag.de/t/f-leftover-tmp-file-if-media-file-could-not-be-opened-for-writing/12001)._