This is not CLR managed-heap memory.
此内存不是clr托管堆内存。
The challenge is that the program is running out of heap memory.
面临的挑战是，程序运行的堆内存。
These two techniques make it possible to avoid heap memory allocation.
这两项技术使人们有可能避免堆内存分配。
The heap memory value in the Profiler will only increase, never decrease.
分析器中的堆内存值仅会增加，而永远不会减少。
The high memory strategy activates metering in the event of prolonged high heap memory usage.
HighMemory策略下，当堆内存使用率长时间处于高位时对活动进行计量。
Traditional GC implementations use a stop-the-world (STW) approach to recovering heap memory.
传统GC实现使用stop - the - world (STW)方法来恢复堆内存。
For instance, a health indicator is used to track the consumption of the database heap memory.
例如，健康指示器可以用来跟踪数据库堆内存的消耗量。
If a memory leak is present in your application, the heap memory usage steadily increases over time.
如果您的应用程序出现了内存泄漏，堆内存使用量将随时间稳步增长。
This means that the new area can start at 0x10580000, contiguous with the heap memory that's already committed.
就是说，新的区域可以从0x10580000 开始，与已经提交的堆空间连接在一起。
After the first collection, free heap memory is primarily the result of objects that were once live but are now dead.
第一次收集后，自由堆内存主要是一些曾经的活对象(现在已死)的结果。
As a result, performance can degrade as the decreased available heap memory leads to more frequent garbage collection.
因此，随着可用堆内存的减少而导致更频繁的垃圾回收，性能可能会降低。
Objects are allocated from the heap; thus the amount of heap memory both used and free are two very important statistics.
对象从堆中分配；因此，使用的和空闲的堆内存数量是两个非常重要的统计信息。
The typical consumer of agent private memory is the sort heap memory that is used by the agent to sort rows during query execution.
代理私有内存的常见消费者是排序堆内存，代理在查询执行期间使用这部分内存来对记录行进行排序。
To cope with the problem of heap memory leak, this paper presents a dynamic memory leak check technology based on red-black tree.
实现时采用红黑树管理所分配的堆内存，理论推导和实验表明其具有较高的效率。
This is done by trading a little bit more CPU cycles and heap memory usage for shorter UI pause time when doing gen 2 collections.
在第2代收集时，用更多CPU周期和堆内存来换取更短的用户界面停顿时间。
Figure 11 shows the GC performance summary graph generated by Tuning Fork, including target utilization, heap memory use, and application utilization.
图11演示了TuningFork所生成的gc性能概要图，包括目标利用率、堆内存使用和应用程序利用率。
Lotus Domino begins using the first two available segments for user heap memory (0x3 and 0x4). Lotus Domino begins using the last segment (0xf) for Shared memory.
LotusDomino最初将前两个可用的段(0x3和0x4)作为用户堆内存，将最后一个段(0xf)作为共享内存。
Prints specific details about the memory at location addr, including its location (stack, heap, text) and, if it is heap memory, then the call chains of its allocation and free history.
打印关于addr单元内存的特殊细节，包括它的储存单元（堆叠，累计，文本）以及，如果它累计了大量内存，还有它的分配调用链和释放历史。
The memory manager relies on the heap being a contiguous slab of memory, so it's impossible to allocate more native memory when the heap needs to expand; all heap memory must be reserved up front.
内存管理器依赖作为相邻内存slab的堆，因此当堆需要扩展时无法分配更多本机内存；所有堆内存必须预先保留。
For most collector implementations, the allocation subsystem keeps a pool of free heap memory, consumed by the application through allocating objects and replenished by the collector through sweeping.
对大多数收集器实现而言，分配子系统持有一个自由堆内存池，应用程序通过分配对象使用该池，然后由收集器通过清理来补充该池。
That is the address in memory in the heap of the first byte that the user typed in.
那是用户输入的第一个字节在内存中堆的地址。
It must be low enough to contain the heap within physical memory.
它必须足够低，以在物理内存的范围内包含堆。
The overflow buffer is used to satisfy peak memory requirements for any heap in the instance Shared memory region whenever a heap exceeds its configured size.
每当某个堆超出了其配置的大小时，便可以使用溢出缓冲区来满足实例共享内存区内任何堆的峰值需求。
Well, there's a chunk of memory called the heap that you can grab as much memory as you want so long as it exists for your program.
好的，这里有一块叫做堆的内存，这样你就可以获得你想要那么多的内存，因为它为你的程序而存在。
If the heap is close to the memory usage of the application, the garbage collector has to collect the heap too often, and performance suffers.
如果堆和应用程序的内存使用量很接近，那么垃圾收集器必须非常频繁地收集堆，这会导致性能损失。
Worse, a cache miss when allocating an object on the heap has a particularly nasty memory interaction.
更糟的是，在堆上分配对象时，缓存遗漏还有一个特别讨厌的内存交互。
Dynamic segment allocation allows the additional segments to be used by user heap or Shared memory.
动态段分配让用户堆或共享内存可以使用额外的段。
If there is enough space in the heap to satisfy a memory request, it can be handled by the language runtime without kernel involvement.
当堆的空间能够满足程序的内存请求时，那么请求的处理过程就可以直接由语言运行时来负责，而不必有系统内核参与。
To ensure the integrity of the heap and the immortal memory area, the RTSJ defines rules for using scoped memory.
为确保堆和不朽内存区域的完整性，RTSJ定义了使用作用域内存的规则。
The most likely type is a memory problem, such as memory leak, heap fragmentation, or large object allocation.
最有可能的类型是内存问题，如内存泄漏、堆碎片、或者大对象分配。
应用推荐