JDK-5073464 : Can we improve error handling for create_itable_stub allocation failure
  • Type: Bug
  • Component: hotspot
  • Sub-Component: runtime
  • Affected Version: 1.4.2,5.0
  • Priority: P4
  • Status: Closed
  • Resolution: Fixed
  • OS: solaris_8,solaris_10
  • CPU: sparc
  • Submitted: 2004-07-13
  • Updated: 2012-12-20
  • Resolved: 2005-08-23
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
6 b47Fixed
Related Reports
Relates :  
JDK-6799919 - Recursive calls to report_vm_out_of_memory are handled incorrectly
Description
JDK: pit build
java version "2d.beta2-jcg-sparc-01-2004-07-12.tiger"
Java(TM) 2 Runtime Environment, Standard Edition (build 2d.beta2-jcg-sparc-01-2004-07-12.tiger)
Java HotSpot(TM) Client VM (build 1.5.0-beta3-b57, mixed mode)
System: Solaris Sparc 10, b61
Locale: zh_CN
Testcase: Java2Demo

Launched Java2Demo, clicked on all the tabs, when clicking on Transform, demo crashed, an log file and core dump were generated.

Log file is attached.

It happened once, couldn't reproduce.

The same test with same build worked fine on WinXP and RedHat AS 3.0

Please change subcategory as appropriate.

Was able to reproduce, see Comments area.

###@###.### 2004-07-13
Comments
EVALUATION Modified CodeCache allocation failure sites to call vm_exit_out_of_memory() instead of fatal(), so that the "check swap space?" hint is displayed on allocation failure.
02-08-2005
CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: dragon
15-09-2004
EVALUATION It was confirmed that this was a user swap space problem. We'll take a look at whether it is possible to handle this particular memory allocation failure more gracefully and/or improve the error message. ###@###.### 2004-07-14
14-07-2004