United StatesChange Country, Oracle Worldwide Web Sites Communities I am a... I want to...
Bug ID: JDK-6226269 JAR verification causes significant footprint increases
JDK-6226269 : JAR verification causes significant footprint increases

Details
Type:
Bug
Submit Date:
2005-02-07
Status:
Resolved
Updated Date:
2010-12-07
Project Name:
JDK
Resolved Date:
2005-04-15
Component:
tools
OS:
windows
Sub-Component:
jar
CPU:
x86
Priority:
P2
Resolution:
Fixed
Affected Versions:
1.4.2_06
Fixed Versions:

Related Reports
Backport:
Backport:
Relates:
Relates:
Relates:
Relates:

Sub Tasks

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

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
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



Hardware and Software, Engineered to Work Together