“Cedar goes farther and does not keep track of which local variables contain pointers; instead, it assumes that they all do. This means that an integer that happens to contain the address of an object which is no longer referenced will keep that object from being freed. Measurements show that less than 1% of the storage is incorrectly retained [45].”

Might this explain/justify the GC bug that 32-bit Go once had[1]?

[1] https://groups.google.com/forum/m/#!topic/golang-nuts/qxlxu5...