下面的列表描述了一些导致内存泄漏的场景。
The following list describes some scenarios that result in memory leaks.
此方法看似容易丢失对象，会导致内存泄漏。
Now, this may seem like an easy way to lose objects, which would result in a memory leak.
这有助于识别导致内存泄漏的潜在无意对象引用。
This helps identify potential unintentional object references causing memory leaks.
不过，该工具不能帮助确定导致内存泄漏的错误源代码。
However, the tool does not aid in identifying the faulty source code responsible for causing the memory leak.
有大量导致内存泄漏的问题，它们对于系统管理员特别棘手。
There are a number of problems that cause memory leaks to be particularly troublesome for System administrators.
还有一些其他的情况可以类似地忽略或破坏对象生命周期管理，并导致内存泄漏。
There are other idioms that can similarly ignore or subvert object lifecycle management and can also lead to memory leaks.
所有者链中的对象的数据类型和包名称有助于标识导致内存泄漏的应用程序组件。
The data types and package names of objects in the owner chain help to identify the application component responsible for the memory leak.
此表标识增长最大的可疑包名称，它可以帮助标识导致内存泄漏的应用程序组件。
This table identifies suspect package names with the largest growth, which can help identify the responsible application component for the memory leak.
导致内存泄漏的应用程序组件通常由构成增长区域的数据类型的包名称和类名称标识。
The application component which is responsible for the memory leak is often identified by the package name and class name of the data types which are part of growing regions.
自动内存管理可解决常见问题，例如，忘记释放对象并导致内存泄漏，或尝试访问已释放对象的内存。
Automatic memory management can eliminate common problems, such as forgetting to free an object and causing a memory leak, or attempting to access memory for an object that has already been freed.
如果源对象生存期超出了侦听器的对象生存期，则常规事件模式会导致内存泄漏：侦听器保持活动状态的时间比预期要长。
Whenever the source object lifetime extends beyond the object lifetime of the listener, the normal event pattern leads to a memory leak: the listener is kept alive longer than intended.
许多内存泄漏是由于程序错误产生的，此类错误导致清除了未调用的方法。
Many memory leaks result due to program errors that cause clean up methods from not getting invoked.
伴随代码稳定性，及进行寿命期测试运行的能力的成功导致了以第三个迭代开始的迭代完成时，增加内存泄漏分析。
Success with code stability, and therefore ability to do longevity test runs, resulted in the addition of memory leak analysis at the completion of an iteration starting with the third.
所属关系以及浏览功能还有助于回答以下问题：是由于什么保留在内存中的泄漏对象上而导致了泄漏？
The ownership relationships, along with the browsing capabilities, also help to answer the question of what is holding on to the leaking objects in memory, thus causing the leak.
这会导致10个字节的内存泄漏。
非代表性测试环境、无效的工作负载标识和不充分的测试周期都可能导致在测试过程中不能检测出内存泄漏。
Non-representative test environments, ineffective workload identification, and insufficient testing cycles cause memory leaks to go undetected through testing procedures.
哪怕及时释放掉了实际的对象，但WPF的弱引用数组还是会继续持有引用，这就导致了内存泄漏。
Even when the actual objects are being released in a timely manner, WPF's arrays of weak references hang around and under stress become the memory leak.
这可导致Out OfMemoryError错误，它实际上不是内存泄漏，而是不适当的配置。
This can lead to OutOfMemoryErrors that are not really memory leaks, but improper configuration.
于是类加载器泄漏(classloaderleaks)就会被引入，导致在连续重部署后内存消耗增加。
So classloader leaks are introduced that lead to increased memory consumption after continuous redeploys.
结果，func函数所分配的20个字节的块就丢失了，并导致了内存泄漏。
As a result, the 20 byte block allocated by the func function is lost and results in a memory leak.
案例研究4：由于无限循环导致的内存泄漏示例。
Case study 4: Example of a memory leak due to an infinite loop.
Purify用来进行内存分析：它帮助寻找应用程序的内存泄漏和错误的内存使用，这些有可能导致应用程序崩溃。
Purify is for memory analysis: it is useful in finding memory leaks and incorrect use of memory in the application, which may be resulting in crashes.
案例研究2：由于未调用的侦听器回调方法而导致的内存泄漏的分析结果。
Case study 2: Analysis results for memory leak due to un-invoked listener call back method.
内存泄漏是导致性能问题的另一可能原因。
Memory leaks are another possible cause of performance problems.
企业应用程序中的内存泄漏会导致大量的危急情况。
Memory leaks in enterprise applications cause a significant number of critical situations.
这有助于避免发生内存泄漏，内存泄漏是导致本机应用程序崩溃的主要原因。
This helps to avoid memory leaks, which are the major cause of crashes among native applications.
这种类型的内存泄漏将会导致您的程序越来越大，运行越来越慢，最终耗尽内存。
This type of memory leak will cause your programs to be bloated, get slower over time, and eventually run out of memory.
可扩展、低开销的内存泄漏分析工具的匮乏导致不能很好地在生产环境和压力测试环境中处理内存泄漏问题。
The lack of scalable and low overhead memory leak analysis tools make it hard to deal with memory leak issues in production or stress test environments.
他所强调的第一种应用就是用其发现普通开发者使用Lucene时的常犯错误：没有关闭IndexReader而导致的内存泄漏。
One he highlighted was a common developer error when working with Lucene: an apparent memory leak caused by the developer failing to close an IndexReader.
他所强调的第一种应用就是用其发现普通开发者使用Lucene时的常犯错误：没有关闭IndexReader而导致的内存泄漏。
One he highlighted was a common developer error when working with Lucene: an apparent memory leak caused by the developer failing to close an IndexReader.
应用推荐