Timeline for Why is checking weird bit errors important in garbage collectors?
Current License: CC BY-SA 3.0
18 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 10, 2015 at 14:47 | comment | added | CodesInChaos | @gnat The GC would exhibit undefined behaviour when encountering corrupted references, just like plain C code would when encountering corrupted pointers. | |
| Dec 10, 2015 at 14:44 | history | reopened | Thomas Owens♦ | ||
| Dec 7, 2015 at 19:01 | comment | added | gnat | think of what happens to gc if references it's supposed to work with are corrupted due to memory errors. What would be result of gc if these references are broken | |
| Dec 7, 2015 at 17:21 | comment | added | hello all | I'm glad my question is answered, but still I don't see how this question is a duplicate of this. Sure, @gnat is the first person to have fired up that duplicate claim, and I read his answer too. That's all about the garbage collector's job of freeing memory with data that are unreachable or unused. Nothing about the garbage collector checking random bit errors in the memory. | |
| Dec 7, 2015 at 17:15 | vote | accept | hello all | ||
| Dec 7, 2015 at 16:45 | comment | added | user40980 | I can find absolutely nothing beyond the assertion of the twitter post that there is any error correction for random memory corruption within Chrome's gc. Do you have any additional material to back this assertion up that one could evaluate? | |
| Dec 7, 2015 at 16:43 | history | closed |
gnat Scant Roger CommunityBot |
Duplicate of What exactly is the Garbage Collector in Java? | |
| S Dec 7, 2015 at 11:40 | history | suggested | Nathan Tuggy | CC BY-SA 3.0 |
Removing misplaced answer, edit mark, left-behind phrasing; threw in an extra tag
|
| Dec 7, 2015 at 9:04 | review | Suggested edits | |||
| S Dec 7, 2015 at 11:40 | |||||
| Dec 7, 2015 at 5:14 | comment | added | user22815 | I am also unclear how a garbage collector would be able to check for these errors (which do occur, although rarely). This is a task for technology such as ECC. How would a garbage collector know what the contents of the memory is? All it does is look for unused blocks to reclaim. | |
| Dec 7, 2015 at 3:43 | history | edited | user40980 | CC BY-SA 3.0 |
Move translation to top so that summary of question is in english.
|
| Dec 6, 2015 at 15:39 | comment | added | Jimmy Hoffa | @gnat if it's unclear in any case at all - don't dupe vote it, vote it unclear. Somebody following dupe chains through closures is just bad experience. | |
| Dec 6, 2015 at 11:59 | history | edited | hello all | CC BY-SA 3.0 |
explained better
|
| Dec 6, 2015 at 11:29 | answer | added | Michael Borgwardt | timeline score: 10 | |
| Dec 6, 2015 at 10:40 | comment | added | CodesInChaos | Perhaps so they don't waste time debugging spurious bug reports caused by random memory errors. That's why redis runs a memory test when it crashes | |
| Dec 6, 2015 at 10:39 | review | Close votes | |||
| Dec 7, 2015 at 16:45 | |||||
| Dec 6, 2015 at 10:24 | comment | added | yannis | @gnat Related yes, duplicate no. | |
| Dec 6, 2015 at 9:09 | history | asked | hello all | CC BY-SA 3.0 |