From: bonnet.jerome@gmail.com   
      
   On Thu, 10 Jul 2025 02:11:48 +0000, bp wrote:   
      
   > 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   
      
   chromium --disable-gpu   
      
   Then everything will run only on CPU and HTOP will tell the real story,   
   you'll likely have heaps of threads spawn, and some idea what it's doing   
   (less hidden then when GPU is processing).   
      
   Have you tried falkon (lighter weight QTWebEngine based Chromium - KDE   
   project work) or iridium (stripped out Google BS code version of   
   chromium)? Do they load the page you're trying to get?   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)