admin管理员组文章数量:1596328
package eliminateObsoleteObject; import java.util.EmptyStackException; //Can you spot the "memory leak" public class Stack { private Object[] elements; private int size = 0; private static final int DEFAULT_INITIAL_CAPACITY = 16; public Stack() { elements = new Object[DEFAULT_INITIAL_CAPACITY]; } public void push(Object o) { ensureCapacity(); elements[size++] = o; } public Object pop(Object o) { if (size == 0) { throw new EmptyStackException(); } // Object result=elements[--size]; // elements[size]=null;//Eliminate obsolete reference // return result; return elements[--size]; } /** * Ensure space for at least one more element,roughly doubling the capacity * each time the array needs to grow. */ private void ensureCapacity() { // TODO Auto-generated method stub } }
Nulling out object references should be the exception rather than the norm.
Generally speaking,whenever a class manages its own memory,the programmer should be alert for memory leaks.Whenever an element is freed,any object references contained it the element should be nulled out.
Another common source of memory leaks is caches.
A third common source of memory leaks is listeners and other callbacks.
Because memory leaks typically do not manifest themselves as obvious failures,they may remain present in a system for years.They are typically discovered only as a result of careful code inspection or with the aid of a debugging tool known as a heap profiler.Therefore,it is very desirable to learn to anticipate problems like this before they occur and prevent them form happening.
转载于:https://wwwblogs/linkarl/p/4808245.html
版权声明:本文标题:Effective Java 英文 第二版 读书笔记 Item 6:Eliminate obsolete object references 内容由热心网友自发贡献,该文观点仅代表作者本人, 转载请联系作者并注明出处:https://m.elefans.com/dongtai/1728256064a1151029.html, 本站仅提供信息存储空间服务,不拥有所有权,不承担相关法律责任。如发现本站有涉嫌抄袭侵权/违法违规的内容,一经查实,本站将立刻删除。
发表评论