What is the difference between a soft reference and a weak reference in Java?

最新推荐文章于 2021-06-18 09:32:50 发布

转载最新推荐文章于 2021-06-18 09:32:50 发布 · 384 阅读

文章标签：

#对象

java 同时被 2 个专栏收录

16 篇文章

订阅专栏

java7

2 篇文章

订阅专栏

本文探讨了弱引用与软引用的概念及应用。弱引用不足以阻止对象被垃圾回收，而软引用则会在内存紧张时才放弃所指向的对象。这两种引用类型能够帮助开发者更高效地管理和缓存对象。

摘要生成于 C知道，由 DeepSeek-R1 满血版支持，前往体验 >

Weak references

A weak reference, simply put, is a reference that isn’t strong enough to force an object to remain in memory. Weak references allow you to leverage the garbage collector’s ability to determine reachability for you, so you don’t have to do it yourself. You create a weak reference like this:

    WeakReference weakWidget = new WeakReference(widget);

and then elsewhere in the code you can use weakWidget.get() to get the actual Widget object. Of course the weak reference isn’t strong enough to prevent garbage collection, so you may find (if there are no strong references to the widget) that weakWidget.get() suddenly starts returning null.

Soft references

A soft reference is exactly like a weak reference, except that it is less eager to throw away the object to which it refers. An object which is only weakly reachable (the strongest references to it are WeakReferences) will be discarded at the next garbage collection cycle, but an object which is softly reachable will generally stick around for a while.
SoftReferences aren’t required to behave any differently than WeakReferences, but in practice softly reachable objects are generally retained as long as memory is in plentiful supply. This makes them an excellent foundation for a cache, such as the image cache described above, since you can let the garbage collector worry about both how reachable the objects are (a strongly reachable object will never be removed from the cache) and how badly it needs the memory they are consuming.

The Sun JRE does treat SoftReferences differently from WeakReferences. We attempt to hold on to object referenced by a SoftReference if there isn’t pressure on the available memory. One detail: the policy for the “-client” and “-server” JRE’s are different: the -client JRE tries to keep your footprint small by preferring to clear SoftReferences rather than expand the heap, whereas the -server JRE tries to keep your performance high by preferring to expand the heap (if possible) rather than clear SoftReferences. One size does not fit all.