ConnectionMultiplexer holding references to 4+ GB memory

We have been having a few instances of our machines low on memory so we were doing a bunch of investigations. In one of the investigations, something peculiar showed up which I could not make a whole lot of sense of.

Here is what dotMemory shows for a specific memory dump.

The string problem we have here, we are aware of it and working on fixing (it doesn't concern caching). The concerning part is 4.04 GB retained by ConnectionMultiplexer

I tried looking deeper into it. It looks like the Redis SDK holds a long Queue of messages

Wanted to understand if this is expected or are we seeing\hitting a bug somewhere, either in the way we are setup OR the way SDK behaves. Also how to interpret this retained memory snapshot in general.

We are using .Net Core 3.1.x Redis caching extension lib which uses StackExchangeRedis 2.0.593

Start with ConnectionMultiplexer and the queued messages shown in the dotMemory snapshots, using the reported .NET Core 3.1.x and StackExchange.Redis 2.0.593 setup. Compare the retained references with normal client behavior and seek a reproducible workload or memory dump. Done means determining whether the retention is expected or identifying a concrete SDK or configuration bug.