What problem are you facing?

While debugging a possible memory leak by creating and analysing some heap snapshots in our Meteor app we discovered an extensive amount of ClientSessions and even some circular references which could prevent garbage collection of unused ClientSessions. The amount of ClientSessions and therefore also the allocated memory is growing substantially even after a few hours of being live in production.

Is the circular reference expected behaviour and are unused ClientSessions properly destroyed after usage?

Attached you can see the MongoClient with the growing array of activeSessions and the circular reference.

What driver and relevant dependency versions are you using?

Meteor version: 2.8.0
Driver version: 4.11.0