For me it happens independently of CPU load. Currently, I'm only working on typping small latex files. That's far away from high CPU load.
I don't use any VM, Virtual Box.
I will see what I can do. :)
I see errors in journalctl if that helps?
Thanks.
For about two months, several times I encountered the following situation: At first single tabs crashed, shortly after restoring tab, the same tab crashes again. Also the other tabs tend to start crashing. After several tabs crashings and restoring, finally the whole browser crashes. Restarting of the browser doesn't work. No GUI appears.
That only happens from time to time. Couldn't see anything which triggers this behaviour.
Crashing tabs. Crashing browser. No restart of browser possible.
No crashing.
Arch linux - up to date. Tor browser download from torproject website.
Verbose output for trying to restart after browser crash. Browser doesn't start again. Final error: Segementation fault (core dumped)
P.S. How can I add line breaks in this markdown code environment, here? My usual method (three empty spaces at the end of the line doesn't seem to work)
$ ./start-tor-browser.desktop --verbose
Launching './Browser/start-tor-browser --detach --verbose'...
Fontconfig warning: "/XXX/tor-browser-linux64-11.0.14_en-US/tor-browser_en-US/Browser/TorBrowser/Data/fontconfig/fonts.conf", line 37: Use of ambiguous path in element. please add prefix="cwd" if current behavior is desired.
Fontconfig warning: "/XXX/tor-browser-linux64-11.0.14_en-US/tor-browser_en-US/Browser/TorBrowser/Data/fontconfig/fonts.conf", line 85: unknown element "blank"
Jul 19 19:25:51.972 [notice] Tor 0.4.7.8 (git-7528524aee3ffe3c) running on Linux with Libevent 2.1.12-stable, OpenSSL 1.1.1o, Zlib 1.2.12, Liblzma N/A, Libzstd N/A and Glibc 2.35 as libc.
Jul 19 19:25:51.972 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://support.torproject.org/faq/staying-anonymous/
Jul 19 19:25:51.973 [notice] Read configuration file "/XXX/tor-browser-linux64-11.0.14_en-US/tor-browser_en-US/Browser/TorBrowser/Data/Tor/torrc-defaults".
Jul 19 19:25:51.973 [notice] Read configuration file "/XXX/tor-browser-linux64-11.0.14_en-US/tor-browser_en-US/Browser/TorBrowser/Data/Tor/torrc".
Jul 19 19:25:51.974 [notice] Opening Control listener on 127.0.0.1:9151
Jul 19 19:25:51.974 [notice] Opened Control listener connection (ready) on 127.0.0.1:9151
Jul 19 19:25:51.974 [notice] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
Jul 19 19:25:51.000 [notice] Parsing GEOIP IPv4 file /XXX/tor-browser-linux64-11.0.14_en-US/tor-browser_en-US/Browser/TorBrowser/Data/Tor/geoip.
Jul 19 19:25:52.000 [notice] Parsing GEOIP IPv6 file /XXX/tor-browser-linux64-11.0.14_en-US/tor-browser_en-US/Browser/TorBrowser/Data/Tor/geoip6.
Jul 19 19:25:52.000 [notice] Bootstrapped 0% (starting): Starting
Jul 19 19:25:52.000 [notice] Delaying directory fetches: DisableNetwork is set.
Jul 19 19:25:52.000 [notice] Starting with guard context "default"
Jul 19 19:25:52.000 [notice] New control connection opened from 127.0.0.1.
Fontconfig warning: "/XXX/tor-browser-linux64-11.0.14_en-US/tor-browser_en-US/Browser/TorBrowser/Data/fontconfig/fonts.conf", line 37: Use of ambiguous path in element. please add prefix="cwd" if current behavior is desired.
Fontconfig warning: "/XXX/tor-browser-linux64-11.0.14_en-US/tor-browser_en-US/Browser/TorBrowser/Data/fontconfig/fonts.conf", line 85: unknown element "blank"
Jul 19 19:25:53.000 [notice] New control connection opened from 127.0.0.1.
Jul 19 19:25:53.000 [notice] New control connection opened from 127.0.0.1.
Jul 19 19:25:53.000 [notice] New control connection opened from 127.0.0.1.
Fontconfig warning: "/XXX/tor-browser-linux64-11.0.14_en-US/tor-browser_en-US/Browser/TorBrowser/Data/fontconfig/fonts.conf", line 37: Use of ambiguous path in element. please add prefix="cwd" if current behavior is desired.
Fontconfig warning: "/XXX/tor-browser-linux64-11.0.14_en-US/tor-browser_en-US/Browser/TorBrowser/Data/fontconfig/fonts.conf", line 85: unknown element "blank"
Exiting due to channel error.
Jul 19 19:25:55.000 [notice] Owning controller connection has closed -- exiting now.
Jul 19 19:25:55.000 [notice] Catching signal TERM, exiting cleanly.
Exiting due to channel error.
./Browser/start-tor-browser: Zeile 362: 195555 Speicherzugriffsfehler (Speicherabzug geschrieben) TOR_CONTROL_PASSWD=${TOR_CONTROL_PASSWD} ./firefox --class "Tor Browser" -profile TorBrowser/Data/Browser/profile.default "${@}" < /dev/null
I have still an other device with an installed Ubuntu. Later, I can check it also on this.
11.0.15
I just checked: 11.0.15 also has set the value to 16384.
The value is set to 16384.
Like I already wrote, I never saw this behaviour before. Tor browser normally always remained with about the same size of used RAM (anything between 4 - 8 GB), and have never really increased much more like that.
I just grabed the privious version of 11.5, which doesn't show this huge RAM usage.
Tor browser generates huge RAM usage. Noticed this issue, because since the newest update my system frozen because of total usage of available memory (RAM + swap = 64GB). After investigation it turned out that tor browser generates this, when watching YouTube videos. With each new video started in a tab it uses 5 - 12 GB on the top! to the already used memory, which is a totally different behaviour to previous versions of tor browser (because of other applications, sometimes, I keep an eye on memory usage ;). Just with closing the tab, the memory get free and available again.
Edit: I just noticed that not all videos raises the memory, or in some cases the raising memory not directly starts with starting the video, instead just after some minutes it suddendly raises the memory by several GB within a minute.
Heavily growing memory usage.
Only slowly growing. In the past, I have never experienced a usage of more than 50% of my available memory of 64GB, even after I had tor browser and a lot of videos running for a lot of days or even weeks.
=> That's a very critical bug, since it can lead fastly to a freezing system for people with small memory.
Arch linux - Up to date. Tor browser dowloaded years ago from torproject website. This bug is related to the newest tor browser release from 14. July 2022: Tor Browser 11.5
Couldn't find any relevant information.