Windows窗体应用程序内存泄漏.NET-WindowsFormsapplicationmemoryleak.NET

1  

Because the memory grows so rapidly, the problem must be in the Paint method of one of the controls (if you paint/draw the control yourself) or in the auto-update loop of your grids (if you update the data source periodically).

因为内存增长如此之快，问题必须出现在其中一个控件的Paint方法中（如果您自己绘制/绘制控件）或者在网格的自动更新循环中（如果您定期更新数据源）。

1. Check if you dispose all Brushes, Pens, Font, StringFormats in your paint loop.
2. 检查是否在绘制循环中处理所有画笔，笔，字体，字符串格式。
3. Check the update-loop of your data sources. Common errors are SqlCommand and SqlConnections which are not disposed properly.
4. 检查数据源的更新循环。常见错误是SqlCommand和SqlConnections没有正确处理。

Hope this helps. Without more detailed information about your source-code it's hard to provide any other help.

希望这可以帮助。如果没有关于源代码的更多详细信息，则很难提供任何其他帮助。

1  

It is possible that your DataSet is not released correctly although you dispose it. From MSDN

尽管您处置了DataSet，但可能无法正确释放它。来自MSDN

Note: Classes inherited from DataSet are not finalized by the garbage collector, because the finalizer has been suppressed in DataSet. The derived class can call the ReRegisterForFinalize method in its constructor to allow the class to be finalized by the garbage collector.

注意：从DataSet继承的类未由垃圾收集器完成，因为终结器已在DataSet中被抑制。派生类可以在其构造函数中调用ReRegisterForFinalize方法，以允许类由垃圾收集器完成。

And you should read this question that can be very usefull Should I Dispose() DataSet and DataTable?

你应该阅读这个非常有用的问题我应该Dispose（）DataSet和DataTable吗？

1  

My employer, Red Gate Software, makes a .NET memory profiling tool you could use to investigate your problem. It has a 14-day trial which might be long enough to find your leak for free :)

我的雇主Red Gate Software制作了一个.NET内存分析工具，您可以使用它来调查您的问题。它有一个为期14天的试用期，可能足够长，可以免费找到你的泄漏:)

http://www.red-gate.com/products/dotnet-development/ants-memory-profiler/

http://www.red-gate.com/products/dotnet-development/ants-memory-profiler/

There is also 'dotTrace Memory' by jetBRAINS, although I've not tried it.

jetBRAINS也有'dotTrace Memory'，虽然我没试过。