Ser*_*eyS 8 .net memory-leaks thread-local
.Net 4. ThreadLocal <>实现IDisposable.但似乎调用Dispose()实际上并不释放对所持有的线程本地对象的引用.
此代码重现了此问题:
using System;
using System.Collections.Generic;
using System.Collections.Concurrent;
using System.Linq;
using System.Threading;
namespace ConsoleApplication2
{
class Program
{
class ThreadLocalData
{
// Allocate object in LOH
public int[] data = new int[10 * 1024 * 1024];
};
static void Main(string[] args)
{
// Stores references to all thread local object that have been created
var threadLocalInstances = new List<ThreadLocalData>();
ThreadLocal<ThreadLocalData> threadLocal = new ThreadLocal<ThreadLocalData>(() =>
{
var ret = new ThreadLocalData();
lock (threadLocalInstances)
threadLocalInstances.Add(ret);
return ret;
});
// Do some multithreaded stuff
int sum = Enumerable.Range(0, 100).AsParallel().Select(
i => threadLocal.Value.data.Sum() + i).Sum();
Console.WriteLine("Sum: {0}", sum);
Console.WriteLine("Thread local instances: {0}", threadLocalInstances.Count);
// Do our best to release ThreadLocal<> object
threadLocal.Dispose();
threadLocal = null;
Console.Write("Press R to release memory blocks manually or another key to proceed: ");
if (char.ToUpper(Console.ReadKey().KeyChar) == 'R')
{
foreach (var i in threadLocalInstances)
i.data = null;
}
// Make sure we don't keep the references to LOH objects
threadLocalInstances = null;
Console.WriteLine();
// Collect the garbage
GC.Collect();
GC.WaitForPendingFinalizers();
GC.Collect();
Console.WriteLine("Garbage collected. Open Task Manager to see memory consumption.");
Console.Write("Press any key to exit.");
Console.ReadKey();
}
}
}
Run Code Online (Sandbox Code Playgroud)
线程本地数据存储对大对象的引用.如果未手动取消引用,GC不会收集这些大对象.我使用任务管理器来观察内存消耗.我也运行内存分析器.垃圾收集后我拍了一张快照.分析器显示泄漏的对象由GCHandle生成,并在此处分配:
mscorlib!System.Threading.ThreadLocal<T>.GenericHolder<U,V,W>.get_Boxed()
mscorlib!System.Threading.ThreadLocal<T>.get_Value()
ConsoleApplication2!ConsoleApplication2.Program.<>c__DisplayClass3.<Main>b__2( int ) Program.cs
Run Code Online (Sandbox Code Playgroud)
这似乎是ThreadLocal <>设计中的一个缺陷.存储所有已分配对象以进一步清理的技巧很难看.关于如何解决这个问题的任何想法?
内存可能已被垃圾回收,但 CLR 进程尚未释放它。它倾向于保留分配的内存一段时间,以备以后需要时使用,因此不必进行昂贵的内存分配。
| 归档时间: |
|
| 查看次数: |
1535 次 |
| 最近记录: |