片语

Corrected The Memory Leak改正记忆漏洞

memory leak error内存溢出错误

memory-leak detection内存泄漏检测

Memory Leak Faults内存走漏故障

heap memory leak堆内存泄漏

memory y leak内存泄漏

Memory Leak Testing内存泄漏测试

Circular-Memory-Leak Mitigation内存泄漏的改进

Memory-leak detection tools内存泄漏发现工具

英汉例句

• figure 1 shows a sample notification generated by the memory leak detection feature.

  图1显示了由内存泄漏检测特性所产生的示例通知。

• there is no use of a coverage tool to measure the code-level code coverage, nor is there use of code quality tools to automate memory leak detection and performance issues.

  覆盖工具对于测量代码级别的代码覆盖来说并没有任何用处，代码质量工具对于自动检测内存泄露和执行问题来说也没有任何用处。

• this identification enables the system administrator to narrow down the root cause of the memory leak to a few component applications.

  这一标识使系统管理员能够将内存泄漏的根源缩小到有限几个组件应用程序中。

• it mimics a memory leak by randomly placing some of these arrays (~20% of them) into a list.

  它通过随机将这些数组的一部分（大约 20%）放入一个列表来模拟内存泄漏。

• for the same reason, moving to 64-bit is no permanent solution to a memory leak — you are just providing more space to leak into, which will only buy time between forced restarts.

  基于此原因，迁移到64位并不是针对内存泄漏的万能解决方案 —您只是增加了可以泄漏的空间，这只是延长了应用程序正常运行的时间。

• 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.

  伴随代码稳定性，及进行寿命期测试运行的能力的成功导致了以第三个迭代开始的迭代完成时，增加内存泄漏分析。

• if a memory leak is present in your application, the heap memory usage steadily increases over time.

  如果您的应用程序出现了内存泄漏，堆内存使用量将随时间稳步增长。

• 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.

  可扩展、低开销的内存泄漏分析工具的匮乏导致不能很好地在生产环境和压力测试环境中处理内存泄漏问题。

• upon detection of a memory leak pattern, this facility will generate multiple heap dumps that have been coordinated with sufficient memory leakage to facilitate comparative analysis using mdd4j.

  在检测到一种内存泄漏方式之后，此工具将产生多重堆转储，它们可以与足够的内存泄漏进行协调，以方便使用mdd4j 的对比分析。

• such a situation is either a sign of a memory leak or of running an application on an application server with too few resources.

  这种情况既可以是内存泄漏的一种标志，也可能表示正在一个资源过少的应用服务器上运行应用程序。

• this tool can be used to analyze (offline) these dumps obtained manually or produced in conjunction with lightweight memory leak detection.

  此工具可用于分析（脱机）手动获取或结合使用轻量级内存泄漏检测生成的这些转储。

• presence of a large number of objects of these types could also signify a deeper memory leak where application objects held by these session objects are actually leaking.

  存在大量的此类对象还意味着更深一层的内存泄漏，即由这些会话对象保留的应用程序对象实际上正在泄漏。

• the memory leak detection rule was designed in accordance with a simple philosophy.

  内存泄漏检测规则是按照一种简单的理念设计的。

• following each run, they would input the runa ?s log into the memory leak analysis tool.

  在每次运行之后，他们会将运行的日志输入到内存泄漏分析工具中。

• also, the test completion details included the results of memory leak analysis following each run.

  同样，测试完成的详情包括每次运行后的内存泄漏分析的结果。

• if the memory leak is exacerbated by certain requests, failures can be intermittent and hard to predict.

  如果内存泄漏由于某些请求而恶化，可能会不断出现错误并且难以预测。

• administrators are able to run lightweight memory leak detection in test and production environments and receive early notification of memory leaks.

  管理员能够在测试或生产环境中运行轻量级内存泄漏检测，并可以在早期接收内存泄漏的通知。

• stress/load testing, memory leak analysis, data integrity testing, and regression testing were all performed due to the extensive automation capabilities exploited by the team.

  由于团队利用大量的自动化功能，因此压力/负载测试、内存泄漏分析、数据完整性测试，和回归测试都将执行。

• once a memory leak has been detected and heap dumps have been generated, they can be transferred outside the production server and into a problem determination machine for analysis.

  一旦已经检测到了内存泄漏并且已经生成了堆转储，它们就可以被传递到生产服务器之外，转到问题确定机器中进行分析。

• prior to each test, the system testers configured several product parameters to allow the memory leak analysis information to be collected during testing.

  在每个测试之前，系统测试人员配置许多产品参数来允许在测试过程中收集内存泄漏分析信息。

• 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.

  在开发迭代中，由于系统测试核心团队早期的测试，与压力相关的及内存泄漏缺陷的子集在正式的系统测试开始之前就被除掉了。

• finding the cause of a memory leak can be a tedious process, not to mention one that will require special debugging tools.

  查找内存漏洞的原因可能是一个乏味的过程，更不用说需要专用调试工具的情况了。

• this heuristic has been found to be effective in a large number of memory leak cases handled in ibm support.

  在大量由ibm支持部门处理的内存泄漏案例中，已经发现这种启发式方法非常有效。

• the graphical user interface provides browsing capabilities for verifiing suspected memory leak regions, and for understanding the data structures that comprise these leaking regions.

  图形用户界面提供浏览功能，以便验证可疑内存泄漏区域和了解组成这些泄漏区域的数据结构。