Message-ID: <6876e462@news.ausics.net> From: not@telling.you.invalid (Computer Nerd Kev) Subject: Re: Chromium on Pi2 Newsgroups: comp.sys.raspberry-pi References: <104lq9r$88hr$1@dont-email.me> <686ef511@news.ausics.net> <1056d1o$8roh$1@dont-email.me> User-Agent: tin/2.6.4-20241224 ("Helmsdale") (Linux/2.4.31 (i586)) NNTP-Posting-Host: news.ausics.net Date: 16 Jul 2025 09:29:38 +1000 Organization: Ausics - https://newsgroups.ausics.net Lines: 33 X-Complaints: abuse@ausics.net Path: nntp.eternal-september.org!news.eternal-september.org!eternal-september.org!feeder3.eternal-september.org!news.bbs.nz!news.ausics.net!not-for-mail druck wrote: > On 10/07/2025 00:02, Computer Nerd Kev wrote: >> The odd thing is that I ran Firefox on x86 with 512MB RAM a >> couple of years ago and it wasn't nearly as bad. > > Have a look at the size of the executable "then" (which is more likely > to be 20 to 25 years ago) No it really was only two or maybe three years ago and Firefox wasn't that much bigger then. > and now, and you'll see why a 512M Zero 2 doesn't stand a chance. The Executable still fits easily in 512MB RAM, for some reason it tries to allocate lots more RAM after starting and displaying the browser window (which seems to work fine for a few seconds before it stalls). It seems the RAM usage increased when they started using multiple processes: https://erahm.org/2016/02/11/memory-usage-of-firefox-with-e10s-enabled/ Maybe on the single-core x86 PC it creates fewer processes and therefore uses less RAM than the quad-core Pi Zero 2? The methods of turning off Firefox's multi-process mode don't seem to work anymore. That also shows how the 64bit builds use significantly more RAM, which will hurt the 64bit RPi Zero 2 but not the 32bit RPi 2. -- __ __ #_ < |\| |< _#