> We've noticed this issue some months ago with bufferevents enabled, > but it's not easy to reproduce or track down [0]. Thanks for pointing me to the ticket, I'll try to keep track of it and help debugging. Sebastian