Your comment isn't wrong in itself. For any GC you can write some program that exploits its weaknesses But you could deal with this bug in various different wa

Your comment isn't wrong in itself. For any GC you can write some program that exploits its weaknesses But you could deal with this bug in various different ways. For example, here you could be implementing erlang queues so that the length is stored, instead of checking the length. You could implement hibernation differently. You could implement popping differently. There are probably ideas from people who know more than nothing about erlang. Anyways, I don't think this particular issue was really an issue with the concept of a GC'd language, more of a specific bug issue.