Path: news.eternal-september.org!eternal-september.org!.POSTED!not-for-mail
From: Lawrence D'Oliveiro <ldo@nz.invalid>
Newsgroups: comp.sys.raspberry-pi
Subject: Re: Chromium on Pi2
Date: Wed, 9 Jul 2025 23:17:21 -0000 (UTC)
Organization: A noiseless patient Spider
Lines: 10
Message-ID: <104mta1$fd02$10@dont-email.me>
References: <104lq9r$88hr$1@dont-email.me> <686ef511@news.ausics.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Injection-Date: Thu, 10 Jul 2025 01:17:21 +0200 (CEST)
Injection-Info: dont-email.me; posting-host="bbe4b1433b47d2d6466a674945d67000";
	logging-data="504834"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX1+rwW5mJqbSr/i7c/5tSD5B"
User-Agent: Pan/0.162 (Pokrosvk)
Cancel-Lock: sha1:YdGioGwNPKw8tQLa+lXLB3ZNf6I=

On 10 Jul 2025 09:02:41 +1000, Computer Nerd Kev wrote:

> I haven't run Chrom(ium) on anything for many years, but it sounds like
> you've run into the same RAM barrier.

If the system runs low on RAM, Linux wakes up its dreaded “OOM Killer” 
kernel thread to free up RAM by killing the most memory-hogging processes. 
You will see evidence of this happening in the logs. If Chromium loses a 
process or two, that might indeed bring operation to a screeching halt 
(though I would expect to see it display error messages as well).