jvm 堆正常 线程分配的内存一直上涨

[guxuan200215]

jstack 5599 查询的结果 threadPoolExecutor-2，threadPoolExecutor-1

"threadPoolExecutor-2" #78 prio=5 os_prio=0 tid=0x00007f72480e6000 nid=0x3d1d waiting on condition [0x00007f7296b21000]
java.lang.Thread.State: WAITING (parking)
at sun.misc.Unsafe.park(Native Method)
- parking to wait for <0x00000000c01844c8> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject)
at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)
at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039)
at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:442)
at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1067)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1127)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:748)

"threadPoolExecutor-1" #77 prio=5 os_prio=0 tid=0x00007f72480e5000 nid=0x3d1c waiting on condition [0x00007f7296e22000]
java.lang.Thread.State: WAITING (parking)
at sun.misc.Unsafe.park(Native Method)
- parking to wait for <0x00000000c01844c8> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject)
at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)
at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039)
at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:442)
at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1067)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1127)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:748)

[guxuan200215]

如图线程分配的字节数一直上涨，有同学知道这是什么问题吗？

[guxuan200215]

这两个线程的分配的内存一直上涨，找不到原因

[zoeg]

1、线程和它的分配内存并不能作为证据，可以参考。 2、jmap -dump:format=b,file=xxx.dmp [pid] 导出java进程的内存快照。你用的这个jvisualvm工具也可以直接生成内存快照，虽然也提供内存快照分析，不过我比较推荐你用IBM HeapAnalyzer，准确地评估你的内存到底哪去了。当然，内存分析需要费点功夫