JDK-6207739 : Return a more specific detail string when OOM due to UseGCTimeLimit instead of "Java heap space"
  • Type: Bug
  • Component: hotspot
  • Sub-Component: gc
  • Affected Version: 6
  • Priority: P4
  • Status: Closed
  • Resolution: Duplicate
  • OS: generic
  • CPU: generic
  • Submitted: 2004-12-13
  • Updated: 2012-02-01
  • Resolved: 2005-12-20
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 7
7Resolved
Related Reports
Duplicate :  
JDK-6287811 - ergonomics OutOfMemoryError should not report as 'java heap space'
Description
Release : Mustang
Build   : 1.6.0-ea-b14

Currently when OOM is thrown due to UseGCTimeLimit, it says "OutOfMemoryError: Java heap space". Please provide a better detail string as "Java heap space" is not appropriate when it is due to UseGCTimeLimit.


###@###.### 2004-12-13 17:37:49 GMT
Comments
EVALUATION initial evaluation by ###@###.### I believe it would not be straight forward to return a detail string that identified the gc time limit as the reason for the out-of-memory. I looked at this at the time I did the implementation. The problem is that the detail string is chosen after an allocation fails and at that point it was not easy to determine that it was because of the gc time limit being exceeded. File a bug as you choose, but I doubt that I would have time to work on it unless customers start to scream. ###@###.### 2004-12-13 17:37:49 GMT
13-12-2004