Tmp dirs in /tmp are not removed

Just by running brave creates alot of temp dirs in /tmp that never are
removed. This is without the browser is even used.
All are empty.

$ ll -d .org*
drwx------ 2 iocc 6 Nov 3 06:54 .org.chromium.Chromium.2sIe9y/
drwx------ 2 iocc 6 Nov 3 11:54 .org.chromium.Chromium.4oyic4/
drwx------ 2 iocc 6 Nov 3 05:14 .org.chromium.Chromium.723Dxd/
drwx------ 2 iocc 6 Nov 3 13:34 .org.chromium.Chromium.DpknR0/
drwx------ 2 iocc 6 Nov 3 05:14 .org.chromium.Chromium.DyGh9E/
drwx------ 2 iocc 6 Nov 3 10:14 .org.chromium.Chromium.eeMXF5/
drwx------ 2 iocc 6 Nov 3 08:34 .org.chromium.Chromium.ejL4u5/
drwx------ 2 iocc 6 Nov 3 05:14 .org.chromium.Chromium.Eqpxt1/
drwx------ 2 iocc 6 Nov 3 08:34 .org.chromium.Chromium.fOIpNL/
drwx------ 2 iocc 52 Nov 3 01:54 .org.chromium.Chromium.haBOjK/
drwx------ 2 iocc 6 Nov 3 13:34 .org.chromium.Chromium.hDuqp7/
drwx------ 2 iocc 6 Nov 3 10:14 .org.chromium.Chromium.HEiZWp/
drwx------ 2 iocc 6 Nov 3 06:54 .org.chromium.Chromium.iABxQs/
drwx------ 2 iocc 6 Nov 3 03:34 .org.chromium.Chromium.JUZ0k4/
drwx------ 2 iocc 6 Nov 3 10:14 .org.chromium.Chromium.Lcn9Vm/
drwx------ 2 iocc 6 Nov 3 11:54 .org.chromium.Chromium.odwz5X/
drwx------ 2 iocc 6 Nov 3 15:14 .org.chromium.Chromium.OuTPRh/
drwx------ 2 iocc 6 Nov 3 15:14 .org.chromium.Chromium.PYHVj0/
drwx------ 2 iocc 6 Nov 3 01:55 .org.chromium.Chromium.qRpvMo/
drwx------ 2 iocc 6 Nov 3 13:34 .org.chromium.Chromium.QXZDF0/
drwx------ 2 iocc 6 Nov 3 15:14 .org.chromium.Chromium.T3iA99/
drwx------ 2 iocc 6 Nov 3 03:34 .org.chromium.Chromium.uGwNFs/
drwx------ 2 iocc 6 Nov 3 11:54 .org.chromium.Chromium.VRJzp9/
drwx------ 2 iocc 6 Nov 3 08:34 .org.chromium.Chromium.x5fWWy/
drwx------ 2 iocc 6 Nov 3 11:55 .org.chromium.Chromium.xmc0fl/
drwx------ 2 iocc 6 Nov 3 05:14 .org.chromium.Chromium.yHioRN/
drwx------ 2 iocc 6 Nov 3 06:54 .org.chromium.Chromium.z7aF3E/
drwx------ 2 iocc 6 Nov 3 03:34 .org.chromium.Chromium.ZqosQm/
drwx------ 2 iocc 6 Nov 3 06:55 .org.chromium.Chromium.zs9uQQ/
$

I have brave-browser-1.71.121-1.x86_64 on alma 9.

I am guessing, not a bug; instead, temporary storage bins for the Chromium engine.

If you delete them, Chromium will likely re-create them during startup.

The problem is that it doesnt delete the empty dirs like it should.
It wasnt like this before.

I havent restarted brave and now its this many:

$ ls -d .org.chromium.Chromium.*
.org.chromium.Chromium.0JkbRr/ .org.chromium.Chromium.jHHTJG/
.org.chromium.Chromium.1PBIsu/ .org.chromium.Chromium.LyV1OF/
.org.chromium.Chromium.2fUeia/ .org.chromium.Chromium.n6oEgC/
.org.chromium.Chromium.3P3vG0/ .org.chromium.Chromium.nPwlVP/
.org.chromium.Chromium.3teraQ/ .org.chromium.Chromium.o02KsY/
.org.chromium.Chromium.40Vs7B/ .org.chromium.Chromium.oNwqcm/
.org.chromium.Chromium.4MyZZT/ .org.chromium.Chromium.PbSvOF/
.org.chromium.Chromium.5lXimR/ .org.chromium.Chromium.PfpUbP/
.org.chromium.Chromium.6du3CR/ .org.chromium.Chromium.PTFiHb/
.org.chromium.Chromium.6nJmJD/ .org.chromium.Chromium.Pwxf9i/
.org.chromium.Chromium.9frnTB/ .org.chromium.Chromium.qu1H6t/
.org.chromium.Chromium.a86sr6/ .org.chromium.Chromium.qyx5GK/
.org.chromium.Chromium.AiEcii/ .org.chromium.Chromium.U1TTOH/
.org.chromium.Chromium.B4kSnU/ .org.chromium.Chromium.UedR3z/
.org.chromium.Chromium.cIokTU/ .org.chromium.Chromium.UmJhMm/
.org.chromium.Chromium.CTlUc1/ .org.chromium.Chromium.UQCwUV/
.org.chromium.Chromium.DAgsYV/ .org.chromium.Chromium.uqPOxQ/
.org.chromium.Chromium.dxFlfh/ .org.chromium.Chromium.uTyqDQ/
.org.chromium.Chromium.dykveR/ .org.chromium.Chromium.vRtx5m/
.org.chromium.Chromium.dYSugF/ .org.chromium.Chromium.weOgwZ/
.org.chromium.Chromium.FFwQfB/ .org.chromium.Chromium.wk0k7z/
.org.chromium.Chromium.fvsOGj/ .org.chromium.Chromium.wujtrm/
.org.chromium.Chromium.gaiByB/ .org.chromium.Chromium.WwB8do/
.org.chromium.Chromium.gOtSA5/ .org.chromium.Chromium.xBeUbL/
.org.chromium.Chromium.H1xMlG/ .org.chromium.Chromium.Yfbi8z/
.org.chromium.Chromium.HpInR3/ .org.chromium.Chromium.ZbMi4y/
.org.chromium.Chromium.itd5QA/ .org.chromium.Chromium.zE4fgI/
.org.chromium.Chromium.Ivi7P8/
$

Not unusual.

Chromium Multi-process Architecture

"https://blog.chromium.org/2008/09/multi-process-architecture.html


The Chromium Projects - Memory Usage Backgrounder
https://www.chromium.org/developers/memory-usage-backgrounder/

Multi-Process Model Background

To understand Chromium’s memory usage, let’s understand the multi-process model. Unlike other browsers, Chromium is divided into multiple processes.

When Chromium starts up, it will initially have two processes.

One process is the browser process which controls the main browser functionality, and the other is the initial renderer process , which runs the Blink rendering engine and JavaScript (V8).

Each time you open a new tab in Chromium, you’ll likely get a new renderer process.

With typical browsing, it is common to see 5-7 chrome.exe processes active.

Further, if you utilize plugins, apps, or extensions, they may also execute within independent processes.

All of Chromium’s processes, whether it is a browser process, a renderer process, or a plugin process, will show under the Task Manager as “chrome.exe”.


April 2020 - Several examples - screenshots - of:

  • Brave Browser Task Manager
  • Windows OS Task Manager


The problem is still that empty tempdirs arent removed just like
the files inside the tempdirs are removed.

$ ls -d .org*|wc -l
192
$

Now its 192 empty dirs.
They might be removed in windows but in linux for this version
they arent. Thats my issue. Chromium Multi-process Architecture
not relevant.

Given that you are using Linux, maybe write a bash shell script that periodically dumps all but the latest 31 tempdirs.


“It” is probably a Chromium engine thing.


May 2019:

Chrome is creating thousands of tmp files in /appdata/local/google/chrome/user data/default/

2017

Chrome keeps writing .tmp files causing 100% disk usage

2023

Linux - Many .org.chromium.Chromium.* directories being created in /tmp

No.
I have reported a bug and Im done here.

Your report is similar to @testingbobby :slight_smile: