Recently we found a bug in our code where the usage of time.After in a tight receive loop caused OOM. I see a similar pattern in consume.go and thought it may be an issue here as well.