如果是的话，将合并内存块以最小化内存碎片。
优化内存碎片整理。提高文件保存和调用倍。
Optimize memory by defragging. Improves file save and recall times.
渲染失败是因为系统运行内存输出或内存碎片太多。
Rendering has been aborted because the system is running out of memory or the memory is too fragmented.
频繁的字体图集重建将迅速降低运行效率，也会导致内存碎片。
Frequent font atlas rebuilds willrapidly degrade runtime performance as well as cause memory fragmentation.
文章指出了这种内存管理机制存在的问题，阐述了内存碎片问题和指针问题。
The problems, such as fragments and Pointers, existing in this kind of memory management method, are presented.
它还会导致系统看起来内存耗尽的情况，因为可用的内存碎片化，没有连续的可用内存。
It can also result in a situation where the system will seem to have run out of memory, because the available memory is fragmented and is not available contiguously.
SACOS的动态内存管理方法可以有效地减少内存管理开销和内存碎片，提高内存的利用率。
The dynamic memory management of SACOS can decrease efficiently the memory management overhead and memory fragmentation and improve the memory utilization.
微软承诺会在.NETFramework 4.5中对此做出改进，其中会有更好的LOH管理，产生的内存碎片会更少。
NET Framework 4.5 promises improvements in this area, with better LOH management and lesser fragmentation.
前两个条目还将RESIDENT参数设置为- 1，这告诉Linux将所有Informix内存碎片保留在内存中，不要将它们交换到磁盘。
The top two also set the RESIDENT parameter to -1, which tells Linux to keep all the Informix memory segments in memory and not swap them to disk.
这么做可以限制内存中 “脏”页面的数量，从而进一步减少I/O开销和磁盘碎片。
The reason for this is to limit the amount of dirty pages in memory, which further reduces I/O overhead and disk fragmentation.
最有可能的类型是内存问题，如内存泄漏、堆碎片、或者大对象分配。
The most likely type is a memory problem, such as memory leak, heap fragmentation, or large object allocation.
G1通过有效的压缩完全避免了对细微空闲内存空间的分配，这不仅大大简化了收集器，而且还消除了潜在的碎片问题。
G1 compacts sufficiently to completely avoid the use of fine-grain free lists for allocation, which considerably simplifies parts of the collector and mostly eliminates potential fragmentation issues.
碎片是一个实际的物理内存块，它存储分区的内容。
A shard is a real, physical chunk of memory that stores the contents of a partition.
因碎片问题或本机内存泄漏而导致的OutOfMemoryError 错误不在本文讨论之列。
OutOfMemoryErrors due to fragmentation issues or due to native memory leaks are beyond the scope of this article.
对于本机内存泄漏，进程大小将增加，对于碎片问题，在发生OutOfMemoryError错误时，会存在大量的可用堆。
For native memory leaks, the process size will increase, and for fragmentation issues, there will be a significant amount of free heap at the time of the occurrence of the OutOfMemoryError.
如图6 所示，spine 中由于内部碎片导致的内存使用开销已经通过将叶子的所有trailing数据包含到spine 中而得到优化。
As Figure 6 illustrates, memory-use overhead that's because of internal fragmentation in the spine has been optimized by including any trailing data for a leaf into the spine.
在分析native_stderr . log时，我们发现垃圾收集周期没有问题，并且不存在内存问题，如内存泄漏、堆碎片和大对象分配。
When analyzing native_stderr.log, we found that the GC cycles were fine, and there were no memory issues, such as memory leak, heap fragmentation, and large object allocation.
因此，必然会引发长时间的暂停来整理碎片或进行压缩，堆将很多小块的自由内存区域整合为一块大的自由内存区域，从而满足大型分配请求。
Consequently, it must incur a long pause to defragment, or compact, the heap to coalesce many smaller free memory areas into larger free memory areas to satisfy a large allocation request.
内存太小或是碎片。
它通过进行游戏目录碎片整理，暂时关闭后台进程，清理内存，达到加强处理器的性能的目的。
It works by defragmenting game directories, temporarily shutting down background processes, cleaning RAM, and intensifying processor performance.
它通过进行游戏目录碎片整理，暂时关闭后台进程，清理内存，达到加强处理器的性能的目的。
It works by defragmenting game directories, temporarily shutting down background processes, cleaning RAM, and intensifying processor performance.
应用推荐