-
Bug
-
Resolution: Fixed
-
P2
-
1.4.2_06
-
beta
-
x86
-
windows
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-2124876 | 5.0u4 | Sean Mullan | P2 | Resolved | Fixed | b03 |
JDK-2125014 | 1.4.2_10 | Nishant Patel | P2 | Resolved | Fixed | b01 |
Java applications using signed JAR files will suffer from significant increase of Java heap footprint. The actual jar verification process will also allocated many additional temporary java objects.
The increased memory footprint is caused by the information with the jar manifest and signature files, which is permanently store in the java heap.
Memory footprint seems to be related with length of jar entry names.
###@###.### 2005-2-07 18:47:31 GMT
The increased memory footprint is caused by the information with the jar manifest and signature files, which is permanently store in the java heap.
Memory footprint seems to be related with length of jar entry names.
###@###.### 2005-2-07 18:47:31 GMT
- backported by
-
JDK-2124876 JAR verification causes significant footprint increases
-
- Resolved
-
-
JDK-2125014 JAR verification causes significant footprint increases
-
- Resolved
-
- relates to
-
JDK-6283161 PIT: Standard Extension test throws ExtensionInstallationException
-
- Resolved
-
-
JDK-6423370 Fix for bug 5098318 prevents caching of JAR files containing cipher code
-
- Resolved
-
-
JDK-6354728 Verification of signed JAR files is very slow (performance reduction)
-
- Resolved
-
-
JDK-6595845 Java 6 JavaWebstart increases footprint by factor 2
-
- Closed
-
(1 relates to)