It had to be another tip request, this time from our garbage collector.
它必须是另一个提示请求，这次来自我们的垃圾收集器。
No event is necessary for this scope because objects associated with it are released by the garbage collector rather than object managers.
这个范围不需要事件，因为与它相关联的对象由垃圾收集器释放，而不是由对象管理器负责。
If there were, the garbage collector would ship with that configuration, and tuning would be unnecessary.
如果有的话，垃圾收集器将提供该配置，那么调整就没有必要了。
There are also many interesting statistics about the garbage collector itself.
还有许多关于垃圾收集器本身的有趣的统计信息。
If response time is more important than highest possible throughput, this garbage collector might be a good choice.
如果响应时间比最高流量更重要，这个垃圾收集器可能是一个不错的选择。
Further, optimizing away some allocations reduces pressure on the garbage collector and allows collection to run less often.
而且，优化掉一些分配，可以降低垃圾收集器的压力，从而让收集运行得更少。
However, their usefulness is tempered by the fact that they rely on the sometimes unpredictable behavior of the garbage collector.
然而，由于它们所依赖的垃圾收集器行为有时候无法预知，所以其实用性就会受到影响。
This way, the garbage collector will obtain more breathing space, decreasing the probability of a full GC.
通过这种方式，垃圾收集器将获得更多空间并减少完全GC的可能性。
This can occur if the program ends prior to the garbage collector freeing the object.
如果程序在垃圾收集器释放对象之前结束，这种情况就可能会出现。
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.
在垃圾收集过程中，垃圾收集器经常吧对象移动到堆中的另外一个位置。
Sorting objects like this allows the garbage collector to examine fewer objects, making each garbage collection quicker.
这样的对象分类允许垃圾收集器检验更少的对象，使每次垃圾收集速度更快。
Next, I added, then deleted four forms and again invoked the garbage collector.
随后，我添加了四个窗体，然后又将它们删除，并再次调用了垃圾收集器。
Each type of reference object has different behaviors, and their interaction with the garbage collector varies.
每种引用对象都有不同的行为，而且它们与垃圾收集器之间的交互也有所不同。
Consider the possibility that the garbage collector may never even run during an application's lifetime.
完全有这样的可能，垃圾收集器在应用程序的生存期内可能始终不会运行。
These new collectors address the problem of the garbage collector being a scalability bottleneck on multiprocessor systems.
这些新收集器是为了解决在多处理器系统中垃圾收集器成为伸缩性瓶颈这一问题的。
When the garbage collector moves an object the garbage collector also updates all handles that refer to the object with the object's new location.
当垃圾收集器移动一个对象时，垃圾收集器会把所有的指向该对象的句柄更新为对象的新地址。
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.
我假设绝大多数人对于使用垃圾收集感兴趣，而不想自己实现一个。
You can also invoke the JVM's garbage collector (GC).
还可以调用JVM的垃圾收集器(GC)。
At this point, the JVM will first attempt to make more memory available by invoking the garbage collector.
当可用内存不能满足需求时，JVM将首先尝试通过调用垃圾收集来释放出更多的可用内存。
Garbage collector and reference interaction.
垃圾收集器和引用交互。
How the garbage collector handles references?
垃圾收集器如何处理references ？
This is also why the garbage collector is called Garbage-First.
这也是为什么该垃圾收集器叫做Garbage - First的原因。
As of Lua 5.1, the garbage collector works incrementally.
在Lua 5.1中，垃圾收集器是以增量方式工作的。
Therefore, if the garbage collector runs after this line, but before line //2, the object will not be reclaimed.
因此，如果垃圾收集器在该行之后（但在行 //2之前）运行，该对象就不会被回收。
This memory cannot be released by the garbage collector.
这个内存不能被垃圾收集器释放。
This configuration provides a balance between how often the garbage collector runs and how long it takes the garbage collector to collect garbage.
此配置在垃圾回收器运行的频率和垃圾回收器进行垃圾回收操作的时间长度之间进行了平衡。
The garbage collector interacts closely with the class loader.
垃圾收集器与类装入器的交互很密切。
The garbage collector interacts closely with the class loader.
垃圾收集器与类装入器的交互很密切。
应用推荐