JDK-6539517 : CR 6186200 should be extended to perm gen allocation to prevent spurious OOM's from perm gen
  • Type: Bug
  • Component: hotspot
  • Sub-Component: gc
  • Affected Version: hs10,6
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2007-03-27
  • Updated: 2011-12-28
  • Resolved: 2008-05-21
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.
JDK 6 JDK 7 Other
6u14Fixed 7Fixed hs13Fixed
Related Reports
Relates :  
Relates :  
Relates :  
Relates :  
Relates :  
Relates :  
Relates :  
Synopsis says it all; refer to CR 6186200.

SUGGESTED FIX In the event that this bug fix is backported to 5uXX or 1.4.2_XX, please make sure to include the changes in CR 6782457 as well so as to avoid a regression. See 6782457 for further details.

EVALUATION The submitter is correct. Fix under construction. Will be available for backport as needed basis given that there's a reasonable workaround and the problem has never been reported from the field as far as we are aware.

SUGGESTED FIX As in synopsis.

WORK AROUND Leave more slop in perm gen via -XX:PermSize=... -XX:MaxPermSize=... and keep JNI critical sections short/bounded.