对于那种“内存引用”，很明显不可以。
In the sense of an actual "memory reference", absolutely not.
始终正确处理返回动态分配的内存引用的函数返回值。
Always properly handle return values of functions returning references of dynamically allocated memory.
有大量的调试工具专门用于分析与内存引用相关的bug。
A number of debugging tools focus on analyzing bugs related to memory references.
此外它还会记录分页空间的进出情况、文件页面的进出情况、候选内存和内存引用。
It also logs paging space in and outs, file page in and outs, candidate memory and memory references.
这种自动内存管理解决了两个最常见的应用程序错误：内存泄漏和无效内存引用。
This automatic memory management resolves the two most common application errors, memory leaks and invalid memory references.
同时，内存管理器排除了出现零碎内存的可能性，并增大了内存引用区域以进一步提高性能。
Meanwhile, the memory manager removes the possibilities of fragmented memory and increases memory locality-of-reference to further increase performance.
从很大程度上说，它避免了本机代码对JVM的直接内存引用，从而确保本机代码只需编写一次，并且可以跨不同的JVM实现或版本运行。
For the most part, it avoids direct memory reference by native code into the JVM, ensuring that natives can be written once and work across different JVM implementations or versions.
通过延迟这些引用或者减少对一些类的引用，您有可能会节约内存和启动时间。
You can potentially save memory and startup time by deferring these references or reducing the reference set of classes.
为每个分区引入了RMO 寄存器，以便引用分区的内存空间中的逻辑零。
The RMO register is introduced for every partition to reference logical zero in the partitioned memory space.
这些引用进一步增加了内存消耗。
需要额外的内存来处理引用。
以前的一篇文章“用弱引用堵住内存泄漏”给出了一些有用的技巧。
A previous article, "Plugging memory leaks with weak references," offers some helpful techniques.
对于托管的代码，帮助找到由于集合中的“未释放的”引用的内存泄漏。
For managed code, helps to find memory leaks due to "living" references in collections.
这些规则控制了作用域之间的许可关系，以及作用域中的对象对其他内存区域中的对象的引用。
These rules control both the relationships allowed between scopes and the allowed references from an object in a scope to objects in other memory areas.
如果引用不弱，那么应用程序会有内存泄漏。
If the references weren't weak, the application would have a memory leak.
正如在上一个示例所暗示的，只有在这些对象引用内存中同一个对象时，它们才是相同的。
As we hinted in our last example, objects are only identical if they refer to the same object in memory.
对象引用视图和对象细节视图：提供对象占用内存的信息。
Object Reference Graph, object References, and object Details views: Provide information about objects holding onto memory.
当从工作内存中移除对象之后，引用该对象的（属于任何规则的）任何条件元素将不被求值。
When an object is removed from the working memory, any conditional elements (of any rule) that had a reference to this object cannot be evaluated now.
任何对内存的间接引用都是通过使用来完成的。
主存中的每个位置都使用连续的数字地址编号，内存位置就使用这个地址来引用。
Every location in main memory is numbered with a sequential numeric address by which the memory location is referred.
这有助于识别导致内存泄漏的潜在无意对象引用。
This helps identify potential unintentional object references causing memory leaks.
大内存页可以用更少的实际页来提供更多的内存，相当于较小的页大小，使用的大内存页越多，就有越多的内存可以通过TLB引用。
Large pages can accommodate more memory in fewer actual pages, so as more large pages are used, more memory can be referenced through the TLB than with smaller page sizes.
引用计数机制为您完成内存管理任务。
为了确保对象之间引用的完整性，RTSJ定义了管理一个内存区域(堆、不朽内存、作用域内存)中的对象如何引用其他内存区域对象的规则。
To ensure the integrity of references between objects, the RTSJ defines rules that govern how objects in one memory area (heap, immortal, or scope) can refer to objects in other memory areas.
当线程执行到所有已知对象都不再被引用的时候，内存域就可以被释放了。
When the thread execution finishes all objects are known to no longer be referenced and the area can be freed.
有时没有被引用的内存会被收集，这样会引发问题，例如，如果一个整数域中包含一个值，该值是已分配内存的地址。
This sometimes leads to problems where memory that isn't referenced is collected if, for example, an integer field contained a value that was the address of allocated memory.
如前所述，进程所引用的内存地址是虚拟地址，需要将其转换成物理地址。
As mentioned before, memory addresses that are referred by a process are virtual addresses and require translation to the physical address.
如以下示例所示，弱引用和软引用都是解决内存泄露的强大工具。
As the following example shows, weak references and soft references are powerful tools for fixing memory leaks.
如以下示例所示，弱引用和软引用都是解决内存泄露的强大工具。
As the following example shows, weak references and soft references are powerful tools for fixing memory leaks.
应用推荐