FULL PRODUCT VERSION :
java version "1.5.0_14"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_14-b03)
Java HotSpot(TM) Client VM (build 1.5.0_14-b03, mixed mode, sharing)
ADDITIONAL OS VERSION INFORMATION :
A DESCRIPTION OF THE PROBLEM :
There is a thread safety problem in the java.util.zip.Deflater native code, which leads to a native memory leak on systems with many processors (seen here on systems with 4 or more) which have many threads using the Deflater in parallel.
You are likely going to try to dismiss this bug as a duplicate of
but it is fact, not.
In digging through the various bug reports relating to that old, unfixed bug, I believe other folks have also run into this issue.
Shows an example (with code) which shows this occurring on systems where the proper workaround for the other leak has been implemented - but the leak is only visible when the Deflater code is exercised in parallel.
STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
Use the Deflater in parallel (2 + threads) on a system 2+ processors.
Observe native memory leak.
This bug can be reproduced always.
CUSTOMER SUBMITTED WORKAROUND :
Single thread all access to the Deflater.