本机内存泄漏。
Problems happen. Applications have memory leaks.
应用程序有内存泄漏问题。
We've all experienced applications with memory leaks.
我们都有过内存溢出的编程经历。
Memory leaks will propagate throughout cluster members.
内存泄漏将在集群成员中传播。
Memory Leaks will propagate throughout cluster members.
内存泄漏将在群集成员中传播。
Heap dumps, which are helpful when hunting for memory leaks.
堆转储，发现内存泄漏时非常有用。
AIX provides the MALLOCDEBUG tool to debug native memory leaks.
AIX提供了MALLOCDEBUG工具，用于调试本机内存泄漏。
See Resources for articles on finding and correcting memory leaks.
有关查找和更正内存泄露问题的文章，请参阅参考资料。
Viewing source code while finding memory leaks in .NET applications
当找到.NET应用程序中的内存泄漏时，查看源代码
If memory leaks were discovered, bug reports were opened and pursued.
如果发现了内存泄漏，那么会打开并追踪故障报告。
The following list describes some scenarios that result in memory leaks.
下面的列表描述了一些导致内存泄漏的场景。
Problems with existing techniques for detecting root causes of memory leaks
用于检测内存泄漏根源的现有技术中所存在的问题
It provides memory diagnostics to aid in detecting and fixing memory leaks.
它提供了内存诊断功能以帮助检测和修复内存泄漏。
This is very useful when troubleshooting performance problems and memory leaks.
这在故障诊断性能问题和内存泄漏时非常有用。
Do you know for sure that there aren't any memory leaks in your running services?
你能肯定的知道正在运行的服务里面没有内存泄露吗？
Easily identify memory leaks by collecting and comparing snapshots of.net memory.
通过收集和比较. NET内存快照简单地识别内存泄漏。
This helps identify potential unintentional object references causing memory leaks.
这有助于识别导致内存泄漏的潜在无意对象引用。
A small amount of prevention will save you later work and embarrassing memory leaks.
只需少量预防工作即可为您省掉大量后续工作，避免令人头疼的内存泄漏问题。
Leak Candidates view: Identifies the objects most likely responsible for memory leaks.
泄漏候选视图：确定最有可能造成内存泄漏的对象。
For managed code, helps to find memory leaks due to "living" references in collections.
对于托管的代码，帮助找到由于集合中的“未释放的”引用的内存泄漏。
Memory leaks in enterprise applications cause a significant number of critical situations.
企业应用程序中的内存泄漏会导致大量的危急情况。
To prevent memory leaks, you must ensure that each allocated object is eventually deleted.
为了防止内存泄漏，必须确保每个分配了内存的对象最终都会被删除。
To be clear, the best approach for solving memory leaks is to detect and resolve them in test.
为了更加清楚起见，解决内存泄漏的最佳方法是在测试时检测并解决它们。
Each application should be carefully tested to ensure that it does not suffer from memory leaks.
应认真测试每个应用程序，以确保它不存在内存泄漏问题。
This is often true with cache implementations, which look very much like a typical memory leaks.
对于缓存实现来说，这一点尤为明显，因为那与典型的内存泄漏极为相似。
A previous article, "Plugging memory leaks with weak references," offers some helpful techniques.
以前的一篇文章“用弱引用堵住内存泄漏”给出了一些有用的技巧。
Many memory leaks result due to program errors that cause clean up methods from not getting invoked.
许多内存泄漏是由于程序错误产生的，此类错误导致清除了未调用的方法。
This helps to avoid memory leaks, which are the major cause of crashes among native applications.
这有助于避免发生内存泄漏，内存泄漏是导致本机应用程序崩溃的主要原因。
Enabling verbose GC is the first step in a problem determination procedure for debugging memory leaks.
启用详细的垃圾收集是在问题确定过程中用于调试内存泄漏的第一步。
Memory debugging programs (see Resources) can come in handy when you're trying to detect memory leaks.
当您试图调试内存漏洞时，内存调试程序(请参阅参考资源)可能派得上用场。
应用推荐