Re:I *detest* the crazy industry politics that made ECC memo...
by themitigating on Sunday October 16, 2022 @01:02PM
(#33225193)
If it crashes then you know the error has occurred, you can then test for that error.
[ Parent
| on HN ]
Re:I *detest* the crazy industry politics that made ECC memo...
by kortex on Sunday October 16, 2022 @01:14PM
(#33225302)
That's assuming the thing you are currently doing is what crashes, and not instead creating data (a document, a compiled binary, a financial transaction, a crypto key) which is silently corrupted and the corruption is only detected way later. C.f. xerox photocopier bug (not saying that was a memory bug, example is an insidious bug).
https://www.dkriesel.com/en/blog/2013/0802_xerox-workcentres...
Re:I *detest* the crazy industry politics that made ECC memo...
by dralley on Sunday October 16, 2022 @01:12PM
(#33225288)
A lot of damage can be done before you get an obvious memory-induced crash. Software crashes all the time for reasons other than memory issues, even someone with deep technical knowledge wouldn't necessarily jump to that conclusion. And everyone else would A) probably never even think of the possibility, B) not know how to test their memory, C) probably buy a whole new laptop instead