为了更加清楚起见，解决内存泄漏的最佳方法是在测试时检测并解决它们。
To be clear, the best approach for solving memory leaks is to detect and resolve them in test.
由于在这些测试环境中重现问题的难度很大，所以相关内存泄漏的成本增加了。
The cost of associated memory leaks is magnified by the difficulty of reproduction in these test environments.
伴随代码稳定性，及进行寿命期测试运行的能力的成功导致了以第三个迭代开始的迭代完成时，增加内存泄漏分析。
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.
同样，测试完成的详情包括每次运行后的内存泄漏分析的结果。
Also, the test completion details included the results of memory leak analysis following each run.
在每个测试之前，系统测试人员配置许多产品参数来允许在测试过程中收集内存泄漏分析信息。
Prior to each test, the system testers configured several product parameters to allow the memory leak analysis information to be collected during testing.
一旦最终的执行在无问题的情况下完成，那么测试人员就会在测试追踪工具的完成记录中加入信息，指示最终的内存泄漏分析的结果。
Once the final run completed without problems, testers included information in the completion records of the test tracking tool, indicating the results of the final memory leak analysis.
在测试过程中，使用各种自动化的技术来启用压力/负载测试、内存泄漏分析、数据完整性测试，和回归测试。
Various automation techniques were employed to enable stress/load testing, memory leak analysis, data integrity testing, and regression testing throughout the test effort.
我们设计了一些通宵运行的单元测试来找出任何内存的泄漏或者稳定性的问题。
We designed some unit tests that would run overnight to identify any heap or stability problems.
RationalPurifyPlus向他通告任何内存泄漏，确保每一行代码都被测试。
Rational PurifyPlus informs him of any memory leaks, and ensures that every line of code is tested.
图6显示了内存泄漏情况的ExploreContext和Contents选项卡，涉及的内容是在IBMWebSpherePortal中进行系统测试过程中发现的缺陷。
Figure 6 shows the Explore Context and Contents TAB for a memory leak case involving a defect found during system testing in IBM WebSphere Portal.
对于内存泄漏的一个简单测试是，在某天的最后一次测试之后让系统继续运行；如果到第二天，该系统恢复到了原始状态，那么您通常可以排除泄漏。
A simple test for memory leaks is to leave the system running after the last test of the day; if the system has recovered to the original state by the next day, then you can often rule out a leak.
管理员能够在测试或生产环境中运行轻量级内存泄漏检测，并可以在早期接收内存泄漏的通知。
Administrators are able to run lightweight memory leak detection in test and production environments and receive early notification of memory leaks.
在开发迭代中，由于系统测试核心团队早期的测试，与压力相关的及内存泄漏缺陷的子集在正式的系统测试开始之前就被除掉了。
During the development iterations, a subset of stress-related and memory leak defects were removed before the formal system test entry time due to the early testing by the system test core team.
应认真测试每个应用程序，以确保它不存在内存泄漏问题。
Each application should be carefully tested to ensure that it does not suffer from memory leaks.
可扩展、低开销的内存泄漏分析工具的匮乏导致不能很好地在生产环境和压力测试环境中处理内存泄漏问题。
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.
非代表性测试环境、无效的工作负载标识和不充分的测试周期都可能导致在测试过程中不能检测出内存泄漏。
Non-representative test environments, ineffective workload identification, and insufficient testing cycles cause memory leaks to go undetected through testing procedures.
WebSphereApplicationServer中的轻量级内存泄漏检测是为了在测试和生产环境中提供内存问题的早期检测而设计的。
Lightweight memory leak detection in WebSphere Application Server is designed to provide early detection of memory problems in test and production environments.
下面是一个例子：在邮件应用程序中发现一个内存泄漏，当该泄漏被处理后，我希望确定在以后的代码改变中不会再发生该问题，于是为此构建了一个单元测试。
Once the leak was fixed, I wanted to make sure the problem wasn't reintroduced in later code changes, so I built a unit test to help prevent this. It's a resource usage unit test, shown in Listing 1.
内存泄漏故障在使用指针的程序中是普遍存在的，采用动态测试方法进行测试难以准确定位故障源。
Memory leak fault is ubiquitous in the program with Pointers. It is difficult to locate fault sources adopting dynamic testing method.
内存泄漏故障在使用指针的程序中是普遍存在的，采用动态测试方法进行测试难以准确定位故障源。
Memory leak fault is ubiquitous in the program with Pointers. It is difficult to locate fault sources adopting dynamic testing method.
应用推荐