原因分析

ThreadLocal 導(dǎo)致內(nèi)存 OOM 的原因是什么？

ThreadLocal 底層通過 ThreadLocalMap 存儲(chǔ)數(shù)據(jù)

源碼如下： 

• 當(dāng)我們使用ThreadLocal.set()時(shí)，set的value與key(即業(yè)務(wù)自己定義的ThreadLocal類)會(huì)存儲(chǔ)在ThreadLocalMap的Entry[]數(shù)組里

源碼如下：

• 其中Entry是實(shí)現(xiàn)了一個(gè)弱引用WeakReference，Entry的key(即業(yè)務(wù)方定義的 ThreadLocal類)會(huì)被包裝成一個(gè)弱引用當(dāng)成Entry的key。Java的弱引用的定義是，當(dāng)JVM執(zhí)行垃圾回收掃描的時(shí)候，當(dāng)發(fā)現(xiàn)只有弱引用的對(duì)象時(shí)，會(huì)立即回收此對(duì)象，這是ThreadLocal當(dāng)初設(shè)計(jì)的時(shí)候防止內(nèi)存溢出的一個(gè)手段

源碼如下： 

雖然key被包裝成了一個(gè)弱引用會(huì)被垃圾回收機(jī)制給回收，但是value在線程(Thread)不死亡時(shí)卻可能存在一條強(qiáng)引用鏈.

由于 value是強(qiáng)引用，只要 Thread不死亡時(shí)，例如線程池，這條強(qiáng)引用鏈就會(huì)存在，那么value就不會(huì)回收，可能造成內(nèi)存溢出

引用關(guān)系如下： Thread ==> ThreadLocalMap ==> Entry ==> value

但是這個(gè)消除強(qiáng)引用鏈的動(dòng)作是需要業(yè)務(wù)方在get的情況下觸發(fā)的，可能業(yè)務(wù)方并不會(huì)get、也可能get是key不為空，并不會(huì)觸發(fā) expungeStaleEntry 類。所以開發(fā)者要養(yǎng)成良好的習(xí)慣，記得用完 ThreadLocal 時(shí)，調(diào)一次ThreadLocal.remove()方法或者 ThreadLocal.set(null)

正確的使用方式

public class ThreadLocalTest {
    /**
     * 未初始化的本地線程變量
     */
    private static ThreadLocal<User> userThreadLocal = new ThreadLocal<>();
    public static void main(String[] args) throws InterruptedException {
        int threadNum = 10;
        List<Thread> threadList = Lists.newArrayList();

        for (int i = 0; i < threadNum; ++i) {
            long userId = i;
            Thread t = new Thread(() -> {
                try {
                    // 設(shè)置變量值
                    userThreadLocal.set(new User(userId, "lanxing" + userId, "2x"));
                    // 使用變量
                    doSomething();
                } finally {
                    // 移除變量
                    userThreadLocal.remove();   //移除ThreadLocal變量
                }
            }, "T" + i);
            threadList.add(t);
            t.start();
        }

        for (int i = 0; i < threadNum; ++i) {
            threadList.get(i).join();
        }
    }
    private static void doSomething() {
        log.info("Use ThreadLocal variable :{}", JSON.toJSONString(userThreadLocal.get()));
    }
}
@Data
@NoArgsConstructor
@AllArgsConstructor
class User {
    private Long id;
    private String name;
    private String level;
}

打印結(jié)果：

14:30:26.790 [T2] INFO io.zhengsh.order.tool.ThreadLocalTest - Use ThreadLocal variable :{"id":2,"level":"2x","name":"lanxing2"}
14:30:26.789 [T5] INFO io.zhengsh.order.tool.ThreadLocalTest - Use ThreadLocal variable :{"id":5,"level":"2x","name":"lanxing5"}
14:30:26.792 [T0] INFO io.zhengsh.order.tool.ThreadLocalTest - Use ThreadLocal variable :{"id":0,"level":"2x","name":"lanxing0"}
14:30:26.792 [T4] INFO io.zhengsh.order.tool.ThreadLocalTest - Use ThreadLocal variable :{"id":4,"level":"2x","name":"lanxing4"}
14:30:26.792 [T8] INFO io.zhengsh.order.tool.ThreadLocalTest - Use ThreadLocal variable :{"id":8,"level":"2x","name":"lanxing8"}
14:30:26.791 [T1] INFO io.zhengsh.order.tool.ThreadLocalTest - Use ThreadLocal variable :{"id":1,"level":"2x","name":"lanxing1"}
14:30:26.792 [T7] INFO io.zhengsh.order.tool.ThreadLocalTest - Use ThreadLocal variable :{"id":7,"level":"2x","name":"lanxing7"}
14:30:26.792 [T6] INFO io.zhengsh.order.tool.ThreadLocalTest - Use ThreadLocal variable :{"id":6,"level":"2x","name":"lanxing6"}
14:30:26.791 [T9] INFO io.zhengsh.order.tool.ThreadLocalTest - Use ThreadLocal variable :{"id":9,"level":"2x","name":"lanxing9"}
14:30:26.790 [T3] INFO io.zhengsh.order.tool.ThreadLocalTest - Use ThreadLocal variable :{"id":3,"level":"2x","name":"lanxing3"}

到此這篇關(guān)于Java中ThreadLocal 導(dǎo)致內(nèi)存 OOM 的原因分析的文章就介紹到這了,更多相關(guān)Java 內(nèi)存OOM 內(nèi)容請(qǐng)搜索腳本之家以前的文章或繼續(xù)瀏覽下面的相關(guān)文章希望大家以后多多支持腳本之家！