From: surname@gmx.net.removethisandtherest.example.invalid   
      
   On 16/08/2025 10:39, frg wrote:   
   > ...>   
   >   
   > Probably an oom. Main reason x86 is done for officially. Has a 10 times   
   > higher crash rate compared to x64 and almost all are out of memory.   
   >...   
      
   Maybe so, but wouldn't the 64-bit versions, using more memory, crash   
   more often on the same hardware (given that the OS and other programs   
   are also bigger)? Or is the problem the per-process address-space limit?   
   If so, splitting the Suite modules into separate processes would improve   
   things without throwing RAM and swap at it. Really, a crappy website   
   (that'll be almost all) shouldn't crash my email. I'm quite surprised   
   that this wasn't implemented back in the day, before FF/TB, as it seems   
   like an easier split than per-tab processes.   
      
   In comparison, Firefox 128ESR doesn't crash at all on these systems   
   because instead it fills the system with processes, none of which get   
   OOMed, until the swap is full and the system becomes unusable (unless   
   it's possible to access one of the console sessions and kill FF to   
   restore usability).   
      
   regards   
   /df   
      
   --   
   London   
   UK   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)