Mozilla engineer Gabriele Svelto posted an update on the Mastodon platform on March 5, providing insights into the causes of Firefox browser crashes and finding that more than 10% of them were caused by physical hardware problems such as memory chip failures.
In its update, Svelto pointed out that by analyzing 470,000 crash reports received within a week, it found that at least 25,000 of them were directly related to memory chip failures and attributed to a “memory bit flip” phenomenon caused by hardware defects.
Note: “Memory bit flips” refers to the phenomenon where binary data (0 or 1) in computer memory unexpectedly flips (0 becomes 1, or 1 becomes 0) due to physical reasons such as hardware aging, cosmic rays, or electromagnetic interference, often leading to program crashes.
Svelto conservatively estimates that hardware issues account for approximately 10% of all Firefox crashes. This data suggests that a significant portion of system crashes are caused by physical defects in the computer, rather than software vulnerabilities left by developers. If crashes due to insufficient available memory are further excluded, the proportion of crashes related to memory data corruption rises to as high as 15%.
To verify these findings on user devices, Mozilla developed a dedicated diagnostic tool. The engineering team instructed users to assess their memory status immediately after an unexpected browser closure. This test was extremely brief, lasting only three seconds, and focused specifically on the first 1GB of running memory (RAM).
