Closed droyo closed 4 years ago
Eek, I guess we never remembered to follow up on this issue -- sorry about that! This is very similar to a patch we applied internally, and in our experience this has effectively fixed the issue in #16. (with credit to @rhalas who discovered and fixed this on our end)
If we don't pass a copy of the
Tread
message to the goroutine that generates theRread
response, The next call toNext
has permission to ovewrite the area of the shared buffer storing the contents ofmsg
.Should fix #16 and #20