Comment 4 for bug 1813104

After running 200 concurrent loggers repeated 10x, and letting the machine sit for a bit, the memory seems to have gone back down.
So it doesn't seem to be a reproducer.

Maybe we have a different bug where clients keep connecting to the controller and not closing the conn. (possible 2.4 vs 2.5 bug?)

Note that ConnectionCount as we have it today counts the number of connections to '/api' but doesn't notice '/logsink' connections.

I looked into adding it, but it isn't trivial because of how the various layers interact. It would certainly be important to add that to the system.