实例共享内存是在数据库管理器启动(db2start)时分配的，并随着数据库管理器的停止(db2stop)而释放。
Instance Shared memory is allocated when the database manager is started (db2start), and freed when the database manager is stopped (db2stop).
这个内存不能被垃圾收集器释放。
如果垃圾收集器需要释放堆中的内存，则这些内存区域将允许任务使用内存而不需要中断任务。
These areas allow tasks to use memory without being required to block if the garbage collector needs to free memory in the heap.
例如，如果排序操作需要更多的内存，而一些缓冲池又有多余的内存，那么内存调优器会释放多余的缓冲池内存，并将它分配给排序堆。
For example, if more memory is needed for sort operations and some buffer pools have excess memory, the memory tuner frees up the excess buffer pool memory and allocates it to the sort heaps.
内存绝不会被应用程序显式释放，而是被垃圾收集器定期回收。
Memory is never explicitly freed by the application but is instead reclaimed periodically by the garbage collector.
使用大部分收集器时，您都无法干涉何时释放内存。
With most collectors, you have no say when your memory is going to be freed.
对象是否被释放取决于垃圾收集器的算法以及垃圾收集器运行时可用的内存数量。
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.
避免在处理器中释放内存的最好方法是，标记或记录将要释放的对象，让程序不间断地检查是否有等待被释放的内存。
The best way to avoid freeing memory in a handler is to flag or record the objects to be freed and have the program check from time to time whether anything is waiting to be freed.
这意味着垃圾收集器释放了MyObject占用的内存，从而使WeakReference对象可以被放在它的Reference Queue上。
This means that the garbage collector freed the memory for MyObject, enabling the WeakReference object to be placed on its ReferenceQueue.
当一台Power服务器的利用率接近它的最大容量时，UPMC工程师开始寻找可以迁移到替代硬件的LPAR，从而释放CPU和内存资源。
Whenever a Power server is utilized to its maximum capacity, UPMC engineers begin looking at LPARs that can be migrated to alternate hardware with the intent of freeing up CPU and memory resources.
这就释放了WebSphere 程序-变更管理员服务器中使用的大量本地内存，而这正是CM 服务器 7.1.0.0 以及7.1.0.1 版本中经常观察到的问题。
This solved the excessive native memory use in the WebSphere Application-Change Manager Server, which was a problem observed with CM Server 7.1.0.0 and 7.1.0.1 releases.
最终，垃圾回收器必须执行回收以释放一些内存。
Eventually the garbage collector must perform a collection in order to free some memory.
本节描述垃圾回收器如何分配和释放内存。
This section describes how the garbage collector allocates and releases memory.
公共语言运行时的垃圾回收器为应用程序管理内存的分配和释放。
The common language runtime's garbage collector manages the allocation and release of memory for an application.
垃圾回收器会自动释放大型对象的内存。
The garbage collector automatically releases the memory for large objects.
这使得垃圾回收器能够释放内存。
垃圾收集器已识别的对象实例，从阵列的麻烦，因此不会收集释放内存。
The garbage collector has trouble identifying object instances that were removed from arrays, therefore would not be collected for releasing of memory.
垃圾回收器执行第0级托管堆的回收后，会压缩可访问对象的内存，如本主题前面的释放内存中所述。
After the garbage collector performs a collection of generation 0, it compacts the memory for the reachable objects as explained in Releasing memory earlier in this topic.
上面我们了解了CLR如何管理托管资源。下面我们来看垃圾收集器如何寻找不再使用的托管对象，并释放其占用的内存。
In previous paragraphs, we learn how CLR manages managed resources. In following paragraphs, we will see how garbage collector find objects no longer needed, and release the memory.
为了解决这一问题，本文设计了高效内存管理器(HPMM)来负责内存单元的申请与释放。
In order to solve this problem we designed the High Performance memory Manager (HPMM) that is responsible for the allocation and deallocation of the memory in F-Miner algorithm.
只有在垃圾回收器(GC)检测到没有任何剩余的活动的引用时，才会终止该实例，并释放与其关联的内存和系统资源。
The instance is terminated, and the memory and system resources associated with it are released, only after the garbage collector (GC) detects that there are no active references remaining.
只有在垃圾回收器(GC)检测到没有任何剩余的活动的引用时，才会终止该实例，并释放与其关联的内存和系统资源。
The instance is terminated, and the memory and system resources associated with it are released, only after the garbage collector (GC) detects that there are no active references remaining.
应用推荐