Leak memory when creating a consumer name with jetstream.

[VuongUranus]

I have problem leaking mem in sync.(*Map).Store in function github.com/nats-io/nats-server/v2/server.getHashSize.
I debug using go tool pprof. Help me please!

[VuongUranus]

[derekcollison]

As a system user what does nats server ls show? How about nats server report jetstream?

[derekcollison]

How many JetStream assets do you have running?

[VuongUranus]

I build a cluster of 3 jetstream nodes to serve to create a lot of ephemeral consumers to receive messages. The number of consumers is more than 10000. And I have a memory leak. The problem is that sync.Map stores the names of the consumers and doesn't release. I use the Go programming language and the nats.go library to do this. Don't know what I did wrong?

[derekcollison]

So you create 10k consumers, then go back to 0 and want the memory to be returned to the kernel?

Or do you think we are not cleaning up an internal client when we create consumers?

[VuongUranus]

I want memory to be freed when consumers are decremented. I see consumers are released very normally, but the problem is that sync.Map in this your code is not freed, leading to memory leak.

[VuongUranus]

[derekcollison]

Thanks will take a look, this is helpful. Much appreciated.

[derekcollison]

Should be resolved and will be in next release, 2.9.21 probably next week.

[VuongUranus]

Thank you very much!!