It got to the title screen, but instead of loading the title screen cinematic behind the logo, it loaded the first map, with a playable Link. You could move around, but the Y axis of the stick was "folded" so you could only ever move backwards, not forwards.
-
Show this thread
-
So yeah, software damage is far from guaranteed to segfault. This is how you get really odd "undebuggable" problems from memory corruption. And how Intel gets away with still crippling desktop CPUs by disabling ECC RAM support.
1 reply 7 retweets 40 likesShow this thread -
Your desktop probably flips a few bits in RAM weekly, but you just don't notice. RAM sizes are too huge for memory to be close to 100% reliable. It just isn't possible without error correction support.
5 replies 8 retweets 46 likesShow this thread -
Replying to @marcan42
Interesting story, but I don't think this is true.
2 replies 0 retweets 0 likes -
"an average of one single-bit-error every 14 to 40 hours per Gigabit of DRAM. The field study also explains that the error-rate increases by the age of the memory. Brand new DRAMs might not show any errors for weeks and months, but then the error-rate suddenly goes up." 1/
2 replies 0 retweets 2 likes -
1 reply 0 retweets 1 like
-
Note that the number is per gigabit, so 8x as much per gigabyte. 3/
1 reply 0 retweets 2 likes -
In a typical consumer PC, for a huge percentage of memory at any given time a random but flip can go unnoticed. The probability that such a bit flip will lead to a crash or obvious error in a short time is vanishingly small. 4/
1 reply 0 retweets 1 like -
In a non-ECC system, a prompt crash would be the second most desirable outcome of a random memory bit flip. Obviously the most desirable would be for the bit flip to occur in memory that is at that time unused. 5/
1 reply 0 retweets 2 likes -
One of the possible outcomes is that the random bit flip happens in a document you're editing, gets saved to disk, and the error enshrined for the life of the document. It may or may not be noticed at some later date. I've experienced that. 6/
3 replies 0 retweets 3 likes
I noticed my first bad RAM bit (back in the Athlon64 days) because I got a syntax error in a system Perl module, as the page cache landed on the bad bit. It didn't persist though, as it wasn't dirtied. I masked off the bad chunk of RAM with a kernel patch and kept using it.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.