P4
FULL PRODUCT VERSION :
java version "1.6.0_07"
Java(TM) SE Runtime Environment (build 1.6.0_07-b06)
Java HotSpot(TM) 64-Bit Server VM (build 10.0-b23, mixed mode)
ADDITIONAL OS VERSION INFORMATION :
Linux machine-name 2.6.18-194.11.1.el5 #1 SMP Tue Jul 27 05:45:06 EDT 2010 x86_64 x86_64 x86_64 GNU/Linux
A DESCRIPTION OF THE PROBLEM :
Executors. returns an ExecutorService which uses a LinkedBlockingQueue. As seen in bug 6806875 LinkedBlockingQueue has a "Young" memory leak. This behaviour is thus seen with any use of the ExecutorService.
It seems reasonable to me to create a long running ExecutorService to run many tasks over time and to expect its memory usage to not behave like this.
STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
see 6806875
REPRODUCIBILITY :
This bug can be reproduced always.
java version "1.6.0_07"
Java(TM) SE Runtime Environment (build 1.6.0_07-b06)
Java HotSpot(TM) 64-Bit Server VM (build 10.0-b23, mixed mode)
ADDITIONAL OS VERSION INFORMATION :
Linux machine-name 2.6.18-194.11.1.el5 #1 SMP Tue Jul 27 05:45:06 EDT 2010 x86_64 x86_64 x86_64 GNU/Linux
A DESCRIPTION OF THE PROBLEM :
Executors. returns an ExecutorService which uses a LinkedBlockingQueue. As seen in bug 6806875 LinkedBlockingQueue has a "Young" memory leak. This behaviour is thus seen with any use of the ExecutorService.
It seems reasonable to me to create a long running ExecutorService to run many tasks over time and to expect its memory usage to not behave like this.
STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
see 6806875
REPRODUCIBILITY :
This bug can be reproduced always.
- duplicates
-
JDK-6805775 LinkedBlockingQueue Nodes should unlink themselves before becoming garbage
-
- Closed
-