I'm trying to switch from mgo to the mongo-go-driver in a relatively simple oplog tailing application. After a few hours, I observe rather high resident memory (multiple GiB). When I take a heap profile, it's implicating connection.ReadWireMessage; specifically "c.readBuf = make([]byte, size)".

This is somewhat similar to GODRIVER-951, but I believe that is caused by a different bug, because in my case, I'm only seeing 16 MiB blocks being allocated, as expected.