错误检测：用户模式下的运行时内存崩溃。
运行时内存错误和泄漏时应用程序中最难检测的问题之一。
Runtime memory errors and leaks are among the hardest problems to detect in an application.
物理限制更多地取决于运行时内存，而不是编译时的各种因素。
Physical limits are dependent more on run-time memory than on compile-time considerations.
堆支持运行时内存分配，和栈不同，大多数语言都允许程序使用堆管理内存。
The heap provides runtime memory allocation, like the stack, meant for data that must outlive the function doing the allocation, unlike the stack. Most languages provide heap management to programs.
开发真正基于C的应用程序的开发团队需要运行时内存工具作为其开发策略的一部分。
Development teams putting out serious C-based applications need a run time memory tool as part of their development strategy.
当利用文档模型使用非常大的文档(通常有5 +MB大小)时，运行时内存的不足会成为一个问题。
Running out of memory can be a problem when using very large documents (generally in the 5 + MB range) with document models.
就像其他运行时内存区一样，本地方法栈占用的内存区也不必是固定大小的，他可以根据需要动态扩展或者收缩。
As with the other runtime memory areas, the memory they occupied by native method stacks need not be of a fixed size. It can expand and contract as needed by the running application.
对象是否被释放取决于垃圾收集器的算法以及垃圾收集器运行时可用的内存数量。
Whether the object is freed depends on the algorithm of the garbage collector as well as the amount of memory available while the collector is running.
在这种情况下，运行时分析结果都在目标内存中得到评价，直到您决定将其返回至主机为止。
In this case, runtime analysis results are evaluated in the target memory endlessly, until you decide to dump them back to the host machine.
类似地，所有对字符串和数组的访问在运行时被检查来确保他们没有越界，消除越界导致的内存重写和数据损坏的问题。
Similarly, all accesses to arrays and strings are checked at run-time to ensure that they are in bounds, eliminating the possibility of overwriting memory and corrupting data.
总的来说，“状态”是指关于程序当前的执行状况的信息——存储在内存中的运行时数据。
In general, "state" refers to information about the current conditions of program execution-runtime data stored in memory.
重要运行时参数的度量，包括内存使用、性能和代码覆盖。
Measurement of vital runtime parameters, including memory usage, performance, and code coverage.
注意：内存可以分配，释放，也可以当数据库正在运行时在不同区域之间交换。
Note: Memory can be allocated, freed, and exchanged between different areas while the database is running.
当运行时，子系统的共享内存包含了实际有用的配置信息。
When running, the subsystem's shared memory contains the actual usable configuration information.
整个数据池在运行时加载入内存。
在使用分区配置文件启动后，DLPAR操作可能会在运行时改变分区资源(包括内存、处理器和适配器)。
DLPAR operation might have altered partition resources (including memory, processor, and adapters) at run time after it is booted with a partition profile.
这些运行时例程的地址可能在每次将JVM加载到内存时变化。
These runtime routines' addresses can be different each time the JVM is loaded into memory.
目的在于避免JIT编译器的运行时性能消耗或内存消耗，或者避免解释程序的早期性能开销。
The goal is either to avoid the JIT compiler's run-time performance or memory cost or to avoid the interpreter's early performance overhead.
要想让运行时成功登录移动设备和上网本还需要对内存与CPU的使用量进行诸多改进。
Much of the work to make the runtime viable on mobile devices and netbooks has been around improving both memory consumption and CPU usage.
扩大功能可以在网格运行时添加内存，并且无需重启。
Scale-out enables memory capacity to be added while the grid is running, without requiring a restart.
这个简单的例程释放运行时分配给接口id向量结构的内存。
This is a simple procedure to free up the memory allocated by the runtime to the interface ID vector structure.
Linux内核调试器(Linux kernel debugger,kdb)是Linux内核的补丁，它提供了一种在系统能运行时对内核内存和数据结构进行检查的办法。
The Linux kernel debugger (KDB) is a patch for the Linux kernel and provides a means of examining kernel memory and data structures while the system is operational.
由于Roo在运行时不存在，它没有任何性能或内存开销。
As Roo does not exist at runtime, it does not have any performance or memory overhead.
理解了heap如何增长以及如何为JVM所用之后，现在您就能更好地理解进程运行时有多少内存被 JVM实际使用。
Now that you understand how the heap grows and is used by the JVM, you can better understand how much memory is actually being used by the JVM while the process is running.
清单11中出现的别名是TypeAlias，它有效地告诉db 4 o用内存中的“a”类型(运行时名称)替换磁盘上的“b”类型(存储的名称)。
The alias at work in Listing 11 is TypeAlias, which effectively tells db4o to swap out an "a" type in memory (the runtime name) for a "b" type on disk (the stored name).
对于一个进程或portal在运行时使用多少内存，存在着一些误解。
Misconceptions can arise about how much memory a process, or portal, uses during runtime.
没错，GlassFish使用了Shoal(运行时的动态集群框架)，它也作为内存复制模块的根基。
Yes, GlassFish USES Shoal, the runtime dynamic clustering framework, which also forms as the basis for in-memory replication module.
如果condition为真，简单使用自动运行时工具不能检测发生的内存泄漏。
Superficial use of automatic run-time tools doesn't detect the memory leak that occurs if the case condition is true.
RationalApplication Developer，即rad，提供一些新的技术，以帮助开发者精确地查找运行时性能和内存相关问题的根源。
Rational Application developer, or RAD, offers several new technologies to help developers pinpoint the source of runtime performance - and memory-related problems.
这使环境变量use_zend_alloc可用于允许在运行时选择malloc或emalloc内存分配。
This makes the environment variable USE_ZEND_ALLOC available to allow selection of malloc or emalloc memory allocations at runtime.
应用推荐