-
Enhancement
-
Resolution: Duplicate
-
P4
-
None
-
5.0
-
x86
-
linux
FULL PRODUCT VERSION :
A DESCRIPTION OF THE PROBLEM :
As reported in bug 6457123, timed waits for instances of java.util.concurrent classes can leak memory. As it is not going to be fixed, this bug should be documented in the Javadoc for the API of Lock, Queue, CountDownLatch, and so forth. Even a short note mentioning the bug number 6457123 would be helpful.
If the problem were documented at the API level, it would likely save thousands - perhaps tens of thousands - of hours of debug time over the coming years.
ACTUAL -
I spent about twenty hours figuring out that the genuinely odd behaviour we were seeing in the production app was due to a memory leak.
REPRODUCIBILITY :
This bug can be reproduced always.
A DESCRIPTION OF THE PROBLEM :
As reported in bug 6457123, timed waits for instances of java.util.concurrent classes can leak memory. As it is not going to be fixed, this bug should be documented in the Javadoc for the API of Lock, Queue, CountDownLatch, and so forth. Even a short note mentioning the bug number 6457123 would be helpful.
If the problem were documented at the API level, it would likely save thousands - perhaps tens of thousands - of hours of debug time over the coming years.
ACTUAL -
I spent about twenty hours figuring out that the genuinely odd behaviour we were seeing in the production app was due to a memory leak.
REPRODUCIBILITY :
This bug can be reproduced always.
- duplicates
-
JDK-6460501 Synchronizer timed acquire still leaks memory
-
- Closed
-
- relates to
-
-
- Resolved
-
-
-
- Closed
-
-
JDK-2143840 Synchronizer timed acquire still leaks memory
-
- Resolved
-