On 7/23/23 10:38 PM, David C. Rankin wrote:
> On 7/23/23 04:59, Carl Spitzer {L Juno} wrote:
>> Complete shut down. Only happens in FF and twice in one day.
>> I think its a FF memory management issue because both times I had >15
>> tabs open.
>
> There is something going on here. I'll run up to 15 or so tabs open
> and I've never had an issue (some JS demands excess CPU, but memory is
> fine)
>
> On the install disk, before you go to sleep, start memtest86+ and let
> it run. It also sounds like you are running into a bad-memory issue.
> When that occurs -- "is like a box of chocolates", but when you it the
> bad address, the system will crash - and it may bring the entire
> system down. With memory address radomization in the Linux virtual
> memory manager -- there is no telling when, or if, any one program
> will have access to the bad RAM.
>
> Firefox, in requesting (and in using in some cases) gigabytes of
> memory -- is one of the more likely apps to hit the bad address....
>
Another issue could be swap on an SSD. We use them because they are
fast. But SSDs have limited write cycles, they get burned out after so
many writes. You could be hitting some burned out sectors on the Swap.