Input: Memory dumps (heap dumps) from the virtual machine (JVM).
输入：来自虚拟机(JVM)的内存转储(堆转储)。
Memory dumps reveal the recorded state of working memory at a specific point in operation.
内存转储呈现运行过程中某一点上WorkingMemory的记录状态。
A parser is required in such cases, which generates meaningful log messages out of those memory dumps.
在这种情况下需要一个解析器，该解析器可以根据这些内存转储生成有意义的日志消息。
Levels are numeric values 0 through 9, where 0 turns debug off for that component and 9 generates the most information, including memory dumps.
其级别使用数字值0到9表示，0关闭组件的调试，而9会生成最多的信息，其中包括内存转储。
These pattern matching algorithms seek to identify aggregated data structures (grouped together by similarity of ownership structure) that are growing the most in between the memory dumps.
这些模式匹配算法可以寻找并标识在内存转储之间增长最快的聚合数据结构(按照类似的所属权结构组合在一起)。
The tool is capable of analyzing very large sized memory dumps (will require 2 GB or more RAM) obtained from production environment application servers encountering OutOfMemoryError issues.
此工具能够分析从遇到Out Of MemoryError问题的生产环境应用程序服务器中获得的非常大的内存转储(将需要2GB或更多的RAM)。
To provide that information, it is necessary to capture allocation stack traces for every object allocation, which is very expensive and is also not available in most formats of memory dumps.
要提供此信息，需要为每个对象分配捕获分配堆栈跟踪，此开销很大，并且在许多格式的内存转储中不可用。
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.
一旦已经检测到了内存泄漏并且已经生成了堆转储，它们就可以被传递到生产服务器之外，转到问题确定机器中进行分析。
This tool can be used to analyze (offline) these dumps obtained manually or produced in conjunction with lightweight memory leak detection.
此工具可用于分析(脱机)手动获取或结合使用轻量级内存泄漏检测生成的这些转储。
This mechanism will generate multiple heap dumps that have been coordinated with sufficient memory leakage to facilitate comparative analysis using MDD4J.
此机制将生成与足够内存泄漏协调的多个堆转储，以便于使用MDD4J 进行比较分析。
Many analysis tools, including MDD4J, analyze heap dumps to find the root cause of a memory leak.
许多分析工具（包括MDD4J）都可以分析堆转储，以找到内存泄漏的根源。
The initial use of system dump is to help diagnose crashes, hangs, or complex memory allocation issues in cases when the other types of dumps are insufficient or cannot be generated.
系统转储的最初用途是在其他类型的转储不够用或无法生成时，帮助诊断崩溃、挂起或复杂的内存分配问题。
RAD's profiling and logging perspective includes views for analyzing your application's memory usage and detecting these leaks through advanced algorithms that compare two heap dumps.
RAD的配置和日志透视包含一些视图，用来分析你的应用程序的内存使用，和通过比较两个堆转储的高级算法来检测这些泄漏。
The initial use of a system dump is to help diagnose crashes, hangs, or complex memory allocation issues in cases when the other types of dumps are insufficient or cannot be generated.
系统转储的最初用途是在其他类型的转储不足或无法生成时，帮助诊断崩溃、挂起或复杂的内存分配问题。
While it might be possible to identify the memory leaking data structure by analyzing the heap dumps, identifying the memory leaking code which is in a infinite loop is not straightforward.
虽然通过分析堆转储能够标识内存泄漏数据结构，但是标识无限循环中的内存泄漏代码并不简单。
This ensures that Heap dumps are taken after evidence of the memory leak is apparent, and with enough memory leakage to ensure the best chance of a valid analysis result.
这可以确保在确定内存泄漏之后获取堆转储，并通过足够的内存泄漏获得最有效的分析结果。
Heap dumps, which are helpful when hunting for memory leaks.
堆转储，发现内存泄漏时非常有用。
Viewing Shared memory data dumps manually on a Linux system.
在Linux系统上手工查看共享内存数据转储。
HeapRoots is an experimental console-based tool for analyzing IBM JDK heap dumps similar to the HAT tool, but it does not pinpoint the root cause of a memory leak.
HeapRoots是一种用于分析IBMjdk堆转储的基于控制台的实验性工具，它类似于HAT工具，但是它不能查明内存泄漏的根源。
On example policy would react to a memory leak notification by taking multiple heap dumps (using workload management to maintain the performance of the application) for analysis.
一种示例策略通过取得多个堆转储(使用工作负载管理来维护应用程序的性能)以进行分析，从而对内存泄漏通知做出反应。
One policy might react to a memory leak notification by taking multiple heap dumps (using workload management to maintain the performance of the application) for analysis.
一种策略通过取得多个堆转储(使用工作负载管理来维护应用程序的性能)以进行分析，从而对内存泄漏通知做出反应。
These dumps contain the entire memory image of the running application - all the information and data in the HPROF format, as well as all of the native-memory and thread information.
这些转储文件包含了运行中应用程序的完整内存镜像—所有信息和数据都采用hprof格式表示，包括所有原生内存和线程信息。
Figure 8 shows the Suspects TAB from the analysis result of two heap dumps taken from a memory leak case involving an infinite loop.
图8中的Suspects选项卡显示了从涉及无限循环的内存泄漏案例中获取的两个堆转储的分析结果。
This one takes the in-memory model and dumps it to a file.
这个文件采用了内存(In - memory)模型，并将其中的内容转储到一个文件中。
Links include: tracking memory allocations, enabling memory diagnostics, taking memory snapshots, viewing memory statistics, and object dumps.
链接包括：跟踪内存分配、启用内存诊断、获取内存快照、查看内存统计信息和对象转储。
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的对比分析。
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的对比分析。
应用推荐