dotnet
msbuild
azure
AsyncLocal never leaks and is safe for CallContext-like state
Even if it's typically used in a static field, the values never leak since they are bound to a transient ExecutionContext
Sometime ago I wrote on How to migrate CallContext to .NETStandard and .NETCore, and one question mentioned that the values themselves might leak, which actually is not the case, as shown here, due to the "magic" that is AsyncLocal in combination with the transient nature of the ExecutionContext:
1
static AsyncLocal<object> local = new AsyncLocal<object>();
2
3
async Task Main()
4
{
5
WeakReference data = null;
6
7
await Task.Run(() =>
8
{
9
var o = new object();
10
data = new WeakReference(o);
11
// We assign to the static async local, to see if it leaks.
12
local.Value = o;
13
});
14
15
// After execution is finished, we do have a live reference still.
16
System.Diagnostics.Debug.Assert(data.IsAlive == true);
17
18
GC.Collect();
19
20
// But a GC proves nobody is holding a strong reference to it.
21
System.Diagnostics.Debug.Assert(data.IsAlive == false);
22
}
Copied!
dotnet - Previous
Use C# 9 records in non-net5.0 projects
Next - dotnet
Using HashCode in .NETFramework
Last modified 1mo ago
Copy link