-
Bug
-
Resolution: Fixed
-
P3
-
1.3.1, 1.4.2, 5.0, 6
-
None
-
b01
-
generic
-
generic
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-2124922 | 6 | Harsha Godugu | P3 | Resolved | Fixed | b63 |
| JDK-2124921 | 5.0u7 | Harsha Godugu | P3 | Resolved | Fixed | b01 |
| JDK-2124462 | 1.4.2_09 | Harsha Godugu | P3 | Resolved | Fixed | b02 |
It's not uncommon for applications that compress large quantities of data to
pass a very large byte array to the Deflater.setInput method, either directly
or via the DeflaterOutputStream.write method. The Deflater code saves a
reference to the given byte array in a private field, and this private field is
never cleared. Since the Deflater class has a finalization method it can take
quite a while for a Deflater instance to be garbage collected, and in the
meantime the potentially-large byte array will be kept alive for no reason.
This has been observed to cause OutOfMemoryErrors under heavy load.
This bug is present in 1.3.1, 1.4.x, 5.0, and Mustang.
###@###.### 2005-1-28 20:22:46 GMT
pass a very large byte array to the Deflater.setInput method, either directly
or via the DeflaterOutputStream.write method. The Deflater code saves a
reference to the given byte array in a private field, and this private field is
never cleared. Since the Deflater class has a finalization method it can take
quite a while for a Deflater instance to be garbage collected, and in the
meantime the potentially-large byte array will be kept alive for no reason.
This has been observed to cause OutOfMemoryErrors under heavy load.
This bug is present in 1.3.1, 1.4.x, 5.0, and Mustang.
###@###.### 2005-1-28 20:22:46 GMT
- backported by
-
JDK-2124462 Unnecessary object retention in java.util.zip.Deflater
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
- relates to
-
-
- Closed
-