Fix memory leak at AssemblyLoadContext unload #69263
Conversation
I have found there was a small memory leak when unloading AssemblyLoadContext. A customer had a quite extreme testing case that ran millions of iterations of creating an AssemblyLoadContext, loading some assemblies into it and then unloading it. After 80 million iterations on their machine with 8GB memory, the testing app was getting out of memory. Using PerfView, I was able to locate the source of the leak. It was a missing destruction of the Module::m_pJitInlinerTrackingMap.
|
Tagging subscribers to this area: @vitek-karas, @agocke, @VSadov Issue DetailsI have found there was a small memory leak when unloading Using PerfView, I was able to locate the source of the leak. It was a I have verified that with the fix applied, the memory doesn't grow at all in
|
|
/backport to release/6.0 |
|
Started backporting to release/6.0: https://github.com/dotnet/runtime/actions/runs/2321924911 |
ghost
locked as resolved and limited conversation to collaborators
I have found there was a small memory leak when unloading
AssemblyLoadContext. A customer had a quite extreme testing case that
ran millions of iterations of creating an AssemblyLoadContext, loading
some assemblies into it and then unloading it. After 80 million
iterations on their machine with 8GB memory, the testing app was getting
out of memory.
Using PerfView, I was able to locate the source of the leak. It was a
missing destruction of the Module::m_pJitInlinerTrackingMap.
I have verified that with the fix applied, the memory doesn't grow at all in
that testing app.