JDK-6226269 : JAR verification causes significant footprint increases
  • Type: Bug
  • Status: Resolved
  • Resolution: Fixed
  • Component: tools
  • Sub-Component: jar
  • Priority: P2
  • Affected Version: 1.4.2_06
  • OS: windows
  • CPU: x86
  • Submit Date: 2005-02-07
  • Updated Date: 2010-12-07
  • Resolved Date: 2005-04-15
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availabitlity Release.

To download the current JDK release, click here.
Other JDK 6
1.4.2_10Resolved 6 betaResolved
Related Reports
Relates :  
Relates :  
Relates :  
Relates :  
Description
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

Comments
EVALUATION The fix for this bug was not quite correct, and the memory is not always being properly released. A new CR 6354728 was opened to address this, and this was fixed in 5.0u7, and targeted for 1.4.2_13.
2006-03-24

EVALUATION Test case was supplied. ###@###.### 2005-2-07 18:47:32 GMT I have a fix for this that uses SoftReferences to hold the Manifest objects, so eventually the memory will be GC-ed. This fix has been tested by Fiducia with success. ###@###.### 2005-03-15 19:07:58 GMT This is also targeted to be fixed in 1.5.0_04. ###@###.### 2005-04-19 13:58:49 GMT
2005-02-07