Possible memory leak about protoactor-go

[rogeralsing]

By the looks of it from the screenshots,
It seems like the Future processes are not cleared out from the local ProcessRegistry.

One thing that caught my eye is this line:
clusterConfig.RequestTimeoutTime = time.Second * 30

Does it look the same if you set that to say 5 seconds? does it flatten out earlier then?

One possible issue could be that futures are not cleared until the timeout expires, even if completed successfully.
I´m not saying this is the case, but if we have such a bug, then it would likely manifest this way.

Another possibility might be if the ConcurrentMap do keep the already allocated size even when entries are removed.

We will have to look deeper into all this.
Any more data from your side would be much appreciated.

[lrweck]

I've seen the same behaviour. From what I could gather, it is the second option (ConcurrentMap keeps already allocated size and does not decrease).

[waeljammal]

Hi, sorry for the late response, I've been away. I'll give your recommendation a try but seems Irweck thinks this might have something to do with ConcurrentMap but I'll give it a shit either way and report back.

[waeljammal]

It still happens after reducing the RequestTimeoutTime to 5 seconds, memory usage keeps going up same as before.

[lrweck]

@rogeralsing have you had the time to check if the memory increase is indeed from ConcurrentMap?