Memory Leak

[websitewill]

I think there is a memory leak with how this is setup.
If you run the demo application and just hold the enter key (force it to do a bunch of requests in the loop) you will see in Process Explorer (or whatever you choose to use), the memory on DemoActor and DemoService increase over time and doesn't ever seem to be released.

I suspect it has something to do with the RemotingContext being static and using those AsyncLocal in the StateDictionary.
Is there something that needs to be done at the end of processing to clear out this memory? Or maybe the leak is somewhere else?

Thanks!
Will

[websitewill]

To add a little detail, the memory does seem to be released, but it takes an incredibly long time - I let the app sit idle and it took about an hour to get back to the start point of ~95K each. Maybe that's just something with how service fabric handles garbage collection? Something to be concerned with/ Anything I can tune here, if not a bug?

[Expecho]

I have to find some time to investigate this :-)