Detailed steps to reproduce the problem?

Connecting a simple Go client to a replica set cluster and the disconnecting it leaves behind RTTMonitor connections that keep sending commands to each Mongo host.

See README in https://github.com/KarboniteKream/mongo-go-rtt-monitor-leak

Definition of done: what must be done to consider the task complete?

Disconnecting a client no longer leaves behind goroutines with runHellos sending commands to Mongo nodes.

The exact Go version used, with patch level:

$ go version
go version go1.21.5 darwin/arm64

The exact version of the Go driver used:

$ go list -m go.mongodb.org/mongo-driver
go.mongodb.org/mongo-driver v1.13.1

Describe how MongoDB is set up. Local vs Hosted, version, topology, load balanced, etc.

Hosted (private cloud) replica set with 3 members, running MongoDB 4.4.17.

The operating system and version (e.g. Windows 7, OSX 10.8, ...)

Client running on macOS 14.2.1 and various Linux flavors (CentOS, Alpine).

Security Vulnerabilities

If you've identified a security vulnerability in a driver or any other MongoDB project, please report it according to the instructions here