Damus
Open in Damus
Gabriele Svelto profile picture
Gabriele Svelto
@Gabriele Svelto
A few years ago I designed a way to detect bit-flips in Firefox crash reports and last year we deployed an actual memory tester that runs on user machines after the browser crashes. Today I was looking at the data that comes out of these tests and now I'm 100% positive that the heuristic is sound and a lot of the crashes we see are from users with bad memory or similarly flaky hardware. Here's a few numbers to give you an idea of how large the problem is. 🧵 1/5
2
Gabriele Svelto · 2w
In the last week we received ~470000 crash reports, these do not represent all crashes because it's an opt-in system, the real number of crashes will be several times larger. Still, out of these ~25000 crashes have been detected as having a potential bit-flip. That's one crash every twenty potential...
Michal Špondr · 2w
nostr:nprofile1qy2hwumn8ghj7un9d3shjtnyd968gmewwp6kyqpqumyuhh5r9yhqxyr7y3clqtvmc6ea6rkldmykeqdg0uvu35ajg43swf2y0d Firefox can consume a large amount of memory. I assume that the more RAM programs use (which web browsers do), the more bit flip errors can be expected. Am I right?