14 ms·
Typically what happens is silent corruption. Rarely, very rarely you'll get a crash, but even if a bit flips inside of program code there's no guarantee that th
by Filligree 9y ago
Typically what happens is silent corruption. Rarely, very rarely you'll get a crash, but even if a bit flips inside of program code there's no guarantee that that code will ever run again -- and if it does, the malfunction might not be obvious.
Most memory is non-program data, however, and most non-program data won't cause obvious errors if corrupted. A picture that renders incorrectly, a broken model in a game, a single burst of static in a video...
It's insidious precisely because it's hard to notice, and corruption never gets better over time.
- blacksmith_tb 9y agoThat certainly makes sense for files, which are read into memory and written back to disk, potentially corrupt - but I wouldn't expect most compiled code to be written back to disk? (I am still on an old cheese-grater Mac Pro, so my 32GB are ECC which means I'm not worried personally, just curious).