| 1. | This results in failure to allocate memory due to virtual address space fragmentation
这样会由于虚拟地址空间碎片而导致内存分配失败。在 |
| 2. | Memory limit : set limits for each component and fail allocations that exceed the limits
内存限制：为每个组件限制它能够使用的最大内存，当超过界限时择存储单元分配失败。 |
| 3. | A condition exists that can subsequently result in an error or critical failure for example , allocation failing or approaching a limit
存在可能在以后导致错误或严重故障（例如，分配失败或接近某一限制）的情况。 |
| 4. | Allocation failure for event 31 , we will see the intervals between gc , the amount of memory recovered , and the duration of the event
（事件31分配失败） ，将会看到gc之间的间隔、恢复的内存数量、事件的持续时间。 |
| 5. | These changes to the large object heap have effectively eliminated memory allocation failures caused by this form of virtual address space fragmentation
对大型对象堆所做的这些更改可有效地消除由虚拟地址空间碎片引起的内存分配失败。 |
| 6. | The other four bufferpools are " hidden " bufferpools , one for each db2 page size 4 k , 8 k , 16 k , and 32 k to ensure db2 can run if the allocation of the user bufferpool fails
其他4个缓冲池是“隐藏的”缓冲池，每个缓冲池对应于一种db2页宽（ 4 k 、 8 k 、 32 k和64 k ） ，这些缓冲池用于确保当用户缓冲池的分配失败时， db2仍能够运行。 |
| 7. | The common language runtime reliability infrastructure distinguishes between aborts and resource allocation failures that occur in " critical " regions of code from those that occur in " non - critical " regions
公共语言运行库可靠性基础结构对以下两个代码区域中出现的中止和资源分配失败进行区分：一个是“关键”代码区域，另一个是“非关键”代码区域。 |
| 8. | If an application gets into a low - memory situation caused by a code bug or inadequate memory that degrades performance , logging a warning event when memory allocation fails might provide a clue about what went wrong
如果一个应用程序处于低内存状态（由于代码bug或内存不足）并导致性能降低，则在内存分配失败时记录一个警告事件可以提供出错原因的线索。 |
