It's challenging to debug firefox. I have 3.5G of RAM, and I added an 8G swapfile, and with that firefox will run under gdb but it takes 15-18 minutes for firefox to start. It uses a lot of swapfile.
Then when you start interacting with is (eg ask it to open a website) it does a hard crash and locks up the system, with no opportunity to backtrace. Turns out gdb logging is off by default -- I'll turn that on and see if I can capture anything before it downs the system. K On 2025-05-12, at 10:36 AM, Ken Cunningham wrote: > It has been working fine up to now, Firefox works fine with MATE, and other > progs are not crashing -- but I haven't run the Apple HW test CD on this > system in a while, not since I replaced the processors after the last time I > changed the power supply about two years ago. > > I'll see if I can get the gdb run done in the next day or two. > > Hopefully some others can chime in further with findings on their own systems > to support / refute their own findings. > > Ken > > > > > On 2025-05-12, at 10:19 AM, John Paul Adrian Glaubitz wrote: > >> Hi, >> >> On Mon, 2025-05-12 at 10:02 -0700, Ken Cunningham wrote: >>> I'll see if I can get it to run under gdb. >>> >>> It's a deep, hard crash -- entire system locked up, no way to reboot, >>> can't log in via SSH, nothing. >>> >>> And nothing displayed in the terminal window to indicate what happened. >> >> Did you verify that the RAM of the system and the GPU are okay? >> >> Adrian >> >> -- >> .''`. John Paul Adrian Glaubitz >> : :' : Debian Developer >> `. `' Physicist >> `- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 >
