JDK-6226269 : JAR verification causes significant footprint increases
- Type: Bug
- Component: tools
- Sub-Component: jar
- Affected Version: 1.4.2_06
- Priority: P2
- Status: Resolved
- Resolution: Fixed
- OS: windows
- CPU: x86
- Submitted: 2005-02-07
- Updated: 2010-12-07
- Resolved: 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 Availability Release.
To download the current JDK release, click here.
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 Availability Release.
To download the current JDK release, click here.
| Other | JDK 6 |
|---|---|
| 1.4.2_10Fixed | 6 betaFixed  |
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
|