有很多问题在SO上问如何检测IDisposable对象泄漏。答案似乎是"你不能"。
我刚刚用最简单的测试用例进行了检查，FxCop 10.0没有做到这一点，ReSharper 4与MSVS2010也没有做到这一点。
对我来说，这似乎是错误的，比C中的内存泄漏更糟糕（至少我们已经建立了检测工具）。
我在想：是否可能使用反射和其他模糊的高级技术，在终结器中注入一个检查，以查看是否已调用Dispose？
WinDBG+SOS的魔术技巧怎么样？
即使没有现有的工具可以做到这一点，我也想知道这在理论上是否可能（我的C#不是很好）。
有什么想法吗？
注意：这个问题的标题可能会误导。真正的问题应该是一个IDisposable对象是否已经正确地Disposed()。被GC处理掉不算，因为我认为那是一个错误。
编辑：解决方案：.NET Memory Profiler可以完成这项工作。我们只需要在程序末尾垃圾回收几次GC.Collect()，以使我们的分析工具能够正确地获取统计数据。
Dispose还是只检测内存？如果我的IDisposable对象只有Console.WriteLine("baz");(我知道这个例子很差，但你明白我的意思)，我想确保它不是由GC调用，怎么办？ - kizzx2您可以通过为IDisposable对象添加Finalizer来实现。在Finalizer中，您可以检查对象是否已被处理。如果未被处理，您可以断言它，或将其写入日志，或执行其他操作。
~Disposable()
{
#if DEBUG
// In debug-builds, make sure that a warning is displayed when the Disposable object hasn't been
// disposed by the programmer.
if( _disposed == false )
{
System.Diagnostics.Debug.Fail ("There is a disposable object which hasn't been disposed before the finalizer call: {0}".FormatString (this.GetType ().Name));
}
#endif
Dispose (false);
}
Disposable中，以此为模板来实现可释放模式。
例如：
/// <summary>
/// Abstract base class for Disposable types.
/// </summary>
/// <remarks>This class makes it easy to correctly implement the Disposable pattern, so if you have a class which should
/// be IDisposable, you can inherit from this class and implement the DisposeManagedResources and the
/// DisposeUnmanagedResources (if necessary).
/// </remarks>
public abstract class Disposable : IDisposable
{
private bool _disposed = false;
/// <summary>
/// Releases the managed and unmanaged resources.
/// </summary>
public void Dispose()
{
Dispose (true);
GC.SuppressFinalize (this);
}
/// <summary>
/// Releases the unmanaged and managed resources.
/// </summary>
/// <param name="disposing">When disposing is true, the managed and unmanaged resources are
/// released.
/// When disposing is false, only the unmanaged resources are released.</param>
[System.Diagnostics.CodeAnalysis.SuppressMessage ("Microsoft.Design", "CA1063:ImplementIDisposableCorrectly")]
protected void Dispose( bool disposing )
{
// We can suppress the CA1063 Message on this method, since we do not want that this method is
// virtual.
// Users of this class should override DisposeManagedResources and DisposeUnmanagedResources.
// By doing so, the Disposable pattern is also implemented correctly.
if( _disposed == false )
{
if( disposing )
{
DisposeManagedResources ();
}
DisposeUnmanagedResources ();
_disposed = true;
}
}
/// <summary>
/// Override this method and implement functionality to dispose the
/// managed resources.
/// </summary>
protected abstract void DisposeManagedResources();
/// <summary>
/// Override this method if you have to dispose Unmanaged resources.
/// </summary>
protected virtual void DisposeUnmanagedResources()
{
}
/// <summary>
/// Releases unmanaged resources and performs other cleanup operations before the
/// <see cref="Disposable"/> is reclaimed by garbage collection.
/// </summary>
[System.Diagnostics.CodeAnalysis.SuppressMessage ("Microsoft.Design", "CA1063:ImplementIDisposableCorrectly")]
~Disposable()
{
#if DEBUG
// In debug-builds, make sure that a warning is displayed when the Disposable object hasn't been
// disposed by the programmer.
if( _disposed == false )
{
System.Diagnostics.Debug.Fail ("There is a disposable object which hasn't been disposed before the finalizer call: {0}".FormatString (this.GetType ().Name));
}
#endif
Dispose (false);
}
}
#if DEBUG 放在了终结器内部，而答案建议使用此代码“作为实现可处理模式的模板”。 - TrueWill@Justin Niessner的建议虽然可行，但我觉得使用完整的分析工具太过繁重。
我创建了自己的解决方案：EyeDisposable。它会检测程序集中未调用Dispose方法的情况。
git submodule update 之前运行 git submodule init。 - Ohad Schneider
IDisposable。如果是的话，我会在它们需要存活的范围内用using包装它们。这对现有代码没有任何作用，但我只是想提一下。 - Nick Strupat