Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Shared memory and deactivated agents #2581
Boris came up with a scenario that doesn't quite meet this and I found one derived from that:
For the first scenario B might be able to use unload to tell A, for the second scenario C is effectively lost with the APIs we provide today (you could do keep-alive pings and that might arguably meet the reliable API definition, but it's not great).
I think there are some solutions here where we could notify the agents within the agent cluster without making GC observable, though applications will have to be careful about cleaning up their objects as they might stay alive longer than desired otherwise. (This "memory leak" versus exposing GC tradeoff is what resulted in this not getting addressed last time around.