How the garbage collector handles references?
垃圾收集器如何处理references ？
Output from the garbage collector, verbose: gc.
垃圾回收器的输出verbose： gc。
You can also invoke the JVM's garbage collector (GC).
还可以调用JVM的垃圾收集器(GC)。
As of Lua 5.1, the garbage collector works incrementally.
在Lua 5.1中，垃圾收集器是以增量方式工作的。
The garbage collector interacts closely with the class loader.
垃圾收集器与类装入器的交互很密切。
Typically a garbage collector is optimised for one or the other.
垃圾收集器通常两者只能顾其一。
Next, I added, then deleted four forms and again invoked the garbage collector.
随后，我添加了四个窗体，然后又将它们删除，并再次调用了垃圾收集器。
Probably. He claims his next move was going to be phoning the garbage collector.
他宣称下一步行动就是给垃圾回收员打电话。
Note the periodic dips corresponding to time quanta where the garbage collector is active.
注意垃圾收集器活动状态下对应于时间量子的周期性下降。
The V8 garbage collector reclaims memory used by objects that can never again be accessed.
V8的垃圾收集器将把不再使用的对象的内存回收掉。
Lazy sweeping improves the response time of the garbage collector and increases its throughput.
懒惰式扫描缩短了垃圾回收器的响应时间，同时还增加了吞吐量。
The garbage collector already does a lot of autonomic tuning to try to optimize its performance.
垃圾收集器为了优化其性能已经执行了很多自动调整。
It can be scheduled when convenient by the JVM and any impact of the garbage collector is immaterial.
JVM可能在任何方便的时候调度它们，垃圾回收产生的影响也是微不足道的。
I assume most of you are more interested in using a garbage collector than implementing one yourself.
我假设绝大多数人对于使用垃圾收集感兴趣，而不想自己实现一个。
My guess is that the garbage collector spends a considerable amount of time with collecting memory.
我猜测垃圾回收器话费了相当多的时间去回收内存。
Consider the possibility that the garbage collector may never even run during an application's lifetime.
完全有这样的可能，垃圾收集器在应用程序的生存期内可能始终不会运行。
If there were, the garbage collector would ship with that configuration, and tuning would be unnecessary.
如果有的话，垃圾收集器将提供该配置，那么调整就没有必要了。
It completes its work when the NHRTs are waiting for more work and the garbage collector is inactive.
在NHRT等待更多工作、垃圾收集器不活动时，它将完成这一工作。
The garbage collector identifies objects that are no longer referenced and reclaim the unused memory.
垃圾回收器可以识别出不再被引用的对象，并回收空闲出的内存。
This way, the garbage collector will obtain more breathing space, decreasing the probability of a full GC.
通过这种方式，垃圾收集器将获得更多空间并减少完全GC的可能性。
At this point, the JVM will first attempt to make more memory available by invoking the garbage collector.
当可用内存不能满足需求时，JVM将首先尝试通过调用垃圾收集来释放出更多的可用内存。
This means improving the garbage collector, optimizing generated code, and improving the core libraries.
这就要改进其垃圾回收器，优化生成的代码，并改进其核心库。
Each type of reference object has different behaviors, and their interaction with the garbage collector varies.
每种引用对象都有不同的行为，而且它们与垃圾收集器之间的交互也有所不同。
This can improve application performance by avoiding the garbage collector unnecessarily shrinking the heap.
这可以避免垃圾收集器对堆进行不必要的收缩，从而改善应用程序性能。
Pooling is quite simple: an object is reused instead of allowing it to be reclaimed by the garbage collector.
池机制相当简单：对象被重新使用，而不是让它被垃圾回收器回收。
If response time is more important than highest possible throughput, this garbage collector might be a good choice.
如果响应时间比最高流量更重要，这个垃圾收集器可能是一个不错的选择。
Memory is never explicitly freed by the application but is instead reclaimed periodically by the garbage collector.
内存绝不会被应用程序显式释放，而是被垃圾收集器定期回收。
During the garbage collection process the garbage collector often moves objects to different locations in the heap.
在垃圾收集过程中，垃圾收集器经常吧对象移动到堆中的另外一个位置。
Therefore, if the garbage collector runs after this line, but before line //2, the object will not be reclaimed.
因此，如果垃圾收集器在该行之后（但在行 //2之前）运行，该对象就不会被回收。
Therefore, if the garbage collector runs after this line, but before line //2, the object will not be reclaimed.
因此，如果垃圾收集器在该行之后（但在行 //2之前）运行，该对象就不会被回收。
应用推荐