Doing so can corrupt the managed heap.
这样做可能会损坏托管堆。
This is looking like a tamping on the managed heap.
这就象一个夯实的动作。
This reserved address space is called the managed heap.
这个保留的地址空间被称为托管堆。
For analyzing the managed heap, however, it is very impressive.
但是，对于分析托管堆，它给人的印象非常深刻。
Each root either refers to an object on the managed heap or is set to null.
每个根或者引用托管堆中的对象，或者设置为空。
The memory that is used by allocated objects on the managed heap surpasses an acceptable threshold.
所用内存分配的对象在托管堆上超过可接受的阈值。
If all the objects in the managed heap survive a collection, then there is no need for memory compaction.
如果托管堆中的所有对象均未被回收，则不需要压缩内存。
First, it is faster to compact the memory for a portion of the managed heap than for the entire managed heap.
首先，压缩托管堆的一部分内存要比压缩整个托管堆速度快。
The garbage collector then promotes these objects and considers this portion of the managed heap generation 1.
然后，垃圾回收器升级这些对象，并考虑第1级托管堆的这一部分。
As long as address space is available in the managed heap, the runtime continues to allocate space for new objects.
只要托管堆中有地址空间可用，运行时就会继续为新对象分配空间。
The CLR Profiler enables you to view the managed heap of a process and investigate the behavior of the garbage collector.
利用CLR探查器，可以查看进程的托管堆并调查垃圾回收器的行为。
The new operator creates the object by allocating the number of bytes required for the specified type from the managed heap.
New算符从受控制的堆里分配指定类型需要的内存来创建对象。
When an application creates the first reference type, memory is allocated for the type at the base address of the managed heap.
应用程序创建第一个引用类型时，将为托管堆的基址中的类型分配内存。
The Garbage Collector runs in its own thread to remove unused memory from your program. It also compacts the managed heap each time it runs.
垃圾收集器以自己的线程运行，从程序里移除未使用的内存，每次运行时也压缩托管堆。
During a collection, the garbage collector examines the managed heap, looking for the blocks of address space occupied by unreachable objects.
在回收中，垃圾回收器检查托管堆，查找无法访问对象所占据的地址空间块。
For example, some software providers may choose a self-managed heap space, while others rely on the underlying operating system (OS) for such functionality.
例如，有些软件提供商可能选择自我管理的堆空间，而其他软件提供商则依赖底层操作系统(OS)来获得这样的功能。
In addition, because new objects that are allocated consecutively are stored contiguously in the managed heap, an application can access the objects very quickly.
另外，由于连续分配的新对象在托管堆中是连续存储，所以应用程序可以快速访问这些对象。
Note that the managed heap is very efficient at allocating new objects, and the garbage collector is very efficient at collecting lots of small and short-lived objects.
请注意，托管堆在分配新对象方面非常有效，而垃圾回收器在收集大量生存期较短的小型对象方面非常有效。
Value types directly contain their state, while reference types are an implicit pair: the named entity is a handle to an unnamed object allocated on the managed heap.
值类型直接包含其状态，而引用类型则是隐式对：命名实体是托管堆上分配的未命名对象的句柄。
This can get rid of the sawtooth pattern often seen for the managed heap size in.net-based applications, and reduces the time an application spends performing garbage collection.
这可以消除基于.NET的应用程序中托管堆大小常见的锯齿模式，并且减少了应用程序为执行垃圾回收而花费的时间。
Scalable Collections on a multiprocessor system running the server version of the execution engine (MSCorSvr. DLL), the managed heap is split into several sections, one per CPU.
可扩展的集合在多处理器系统上运行的执行引擎的服务器版本(mscorsvr。DLL)，托管堆分成几个部分，每一个CPU。
After the garbage collector performs its first collection of generation 0 and promotes the reachable objects to generation 1, it considers the remainder of the managed heap generation 0.
在执行第0级托管堆的首次回收并把可访问的对象升级至第1级托管堆后，垃圾回收器将考虑第0级托管堆的其余部分。
For example, even the use of container classes from the standard JCL must be carefully managed so that the container class doesn't unintentionally create temporary or internal objects on the heap.
例如，即使使用标准JCL中的容器类也必须小心，以避免容器类无意中为堆创建临时或内部对象。
We rarely if ever need to create a heap bucket explicitly: rather they are managed internally when we use the stdio-like API to write data to the next filter.
如果有过需要显式创建一个堆桶，我们很少这样做：更多的是他们被内部管理，当我们使用成套的API来写数据给下一个过滤器时。
This is not CLR managed-heap memory.
此内存不是clr托管堆内存。
This is not CLR managed-heap memory.
此内存不是clr托管堆内存。
应用推荐