Hello everybody,
I’ve just opened /tmp and realized that a lot of empty files are being while dolphin is opened. Is this a known bug?
Such a temp files are currently needed to write per-folder view settings.
They are supposed to be closed and deleted once they are not needed anymore. It seems there is an issue there.
/tmp directory is flushed (i.e emptied) at each reboot, and the files are very small usually, so this shouldn’t cause real issues.
Work is ongoing to remove the need for those tmp files.
1 Like
In fact the /tmp directory is in-memory on most distros, and nothing is written to disk.
You can have a look with: df /tmp
I see:
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 16388760 16 16388744 1% /tmp
If the filesystem is tmpfs like it is for me (it’s the default on Fedora), then it’s in-memory.
Once all dolphin windows are close you can remove those.
Thanks for your reply. I find it very excessive to have 0byte files to the tunes of thousands. Especially if there’s no boundaries it could lead to inode exhaustion.
Is your /tmp on disk or in memory? (See above posts for how to check.)
That does seem like a potential concern for in-memory filesystems - https://serverfault.com/a/524436
Btw it has been reported:
Reporting a bug or subscribing to one allow to follow the bug resolutions efficiently.
What is your distro @Nolaan ?
On Arch I don’t reproduce with /tmp in tmpfs.