JDK-6382700 : Default compile policy in javac causes footprint issues
- Type: Bug
- Component: tools
- Sub-Component: javac
- Affected Version: 6
- Priority: P2
- Status: Resolved
- Resolution: Fixed
- OS: generic
- CPU: generic
- Submitted: 2006-02-08
- Updated: 2010-04-03
- Resolved: 2006-05-13
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.
| JDK 6 |
|---|
6 b85Fixed  |
Related Reports
|
Relates :
|
|
|
Relates :
|
Description
http://blogs.sun.com/ahe?entry=upcoming_compiler_fixes#comment1 The compiler in Mustang seems to require too much memory for compilation. When given 300MB, it fails to compile our project (actually a part of it consisting of ~10000 classes) with "out of resources" message. The same configuration works ok in Tiger. Is it a known issue?
Comments
|