|
| ▲ | jesup a day ago | parent | next [-] |
| You should look at about:crashes and see if there's any commonality in the causes, or bugs associated with them (though often bugs won't be associated with the crash if it isn't filed from crash-stats or have the crash signature in the bug) |
|
| ▲ | antonf a day ago | parent | prev | next [-] |
| Maybe you should check your memory? I recently started to get quite a lot of Firefox crashes, and definitely contributed to this statistic. In the end, the problem was indeed memory - crashes stopped after I tuned down some of the timings. And I used this RAM for a few years with my original settings (XMP profile) without issue. |
| |
| ▲ | aforwardslash 13 hours ago | parent [-] | | I experience them in several different devices; On my main device, I have hundreds of chrome tabs and often many workloads running that would be completely corrupt with random bit flips. I'm not discarding the possibility of faulty RAM completely, I just take the measurement of the tweet with a huge grain of salt - after all, I still remember when the FF team constantly denied - for more than half a decade - that the browser had serious memory leak problems, so its not like there isn't a history of pointing out other causes for FF crashes. |
|
|
| ▲ | squeaky-clean 20 hours ago | parent | prev [-] |
| The last time I can recall Firefox crashing was when I was using Windows Vista. This definitely sounds like a problem with your system. |
