ungoogled-chromium portable making a lot of .TMP files that never clear themselves.

[Ergonomicmike]

First, thanks for maintaining ungoogled-chromium portable. I have been using the previous version for a year now.

I expanded 127.0.6533.89.7z to a new folder in Windows 10.

The page here says that "--disable-logging" is passed to the executable. But in my instance it is generating a log file anyway.

So then I tried using ungoogled-chromium-portable.yml to disable logging. And to enable cleaning.

The first problem I had using the .yml is that it seems to be hard-coded to expect chrome.exe.

So after I added the path to the portable for the app_path (without quotes) and renamed ungoogled-chromium-portable.exe to chrome.exe, I receive a "Failed Command" window in Windows.

I cannot kill that process and I have to reboot Windows to clear it.

While I am reporting issues, I have also noticed that ungoogled.chromium,portable grows a LOT of .tmp files. Most of them have the suffix TransportSecurity~. Some have the suffix LOG.old~ None which ever seem to clear themselves. (Which is why I tried enabling the clean function in .yml.)

Is it just me? I have a very "hacked" version of Win10, where I've used NTLite to remove a lot of Windows components for security.

(As I write this, it ocurrs to me that I should try running ungoogled-chromium-portable in a vanilla Win10 in a VM to see if the problem follows Windows or if it follows the portable app.)

[Ergonomicmike]

Oops - never mind on the .yml file not working. I failed to realize that the app_path for the "app" is to the chrome executable in ungoogled-chromium-portable\app. (Not to the portable executable.) After that change, it has stopped generating a log file.

[Ergonomicmike]

I installed the latest Release dated Nov 2024, v 130.0.6723.122 - 19. The problem with the .tmp files not clearing themselves still exists.

The screen shot shows 1755 .tmp files so far. (I've seen as many as 7000 in the previous Release.) For this screen shot, my computer has been up for 1 day since last reboot. I sorted the list by Oldest to show .tmp files from two days ago, to show that they survived closing ungoogled-chrome, the subsequent reboot, and re-open of ungoogled-chrome.

Is it just me? I run ungoogled-chrome portable virtualized (Comodo). But I have disabled HIPS with not much change in this behavior.

I suppose I could create a chron job in Windows' Task Scheduler, a command line delete, to delete the .tmp's once a day. For now, I just manually delete the .tmp's.