Gabriele Svelto on Nostr: A few years ago I designed a way to detect bit-flips in Firefox crash reports and ...
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
Published at
2026-03-04 16:03:58 UTCEvent JSON
{
"id": "25c702e1414bc4913b1d9aaaec858644f366aa208e6badca264ec8c509d93619",
"pubkey": "65e8e1c000c3b1b272480a5b2be804dae8e45d83466ab9cbfd22dc0744fbf849",
"created_at": 1772640238,
"kind": 1,
"tags": [
[
"proxy",
"https://mas.to/@gabrielesvelto/116171750653898304",
"web"
],
[
"proxy",
"https://mas.to/users/gabrielesvelto/statuses/116171750653898304",
"activitypub"
],
[
"L",
"pink.momostr"
],
[
"l",
"pink.momostr.activitypub:https://mas.to/users/gabrielesvelto/statuses/116171750653898304",
"pink.momostr"
],
[
"-"
]
],
"content": "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",
"sig": "f40ef1c67b2c810d645f21a6ed318bdcc9e35b9027771b7ddbefb31e5e55163313c671c658f7ce04b390125f0d6f719f25799b760fc93bf5cf09e6f150f8a4cd"
}
