Re: Chromium on Pi2

Lawrence D'Oliveiro <ldo@nz.invalid> wrote:

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).

This is a Pi2, so 1 gig RAM. I've not messed with the CPU/GPU memory
allocation, it's default AFAIK.
 
A quick look at Task Manager suggests less than half a gig of RAM in use,
htop reports the same with 100M of swap in use out of 500M available.
This is on a somewhat elderly microSD in a default image as distributed
from the Raspberry Pi website.

The task manager is also reporting 0% cpu for all the chromium processes.
That's rather odd. At the moment chromium is trying to re-open its window
after being iconified and it's making no progress. After a couple of tries
the "close window" (top right x) got rid of the window. 

There are also two "chrome_crashpad_handler" processes, 0% cpu.
Might that be a hint chromium has crashed, and the handler that
generates the "aw snap" dialog crashed too?

thanks for reading!

bob prohaska