JDK-6280629 : Need ability to dump the heap at OutOfMemoryError
  • Type: Enhancement
  • Component: core-svc
  • Sub-Component: tools
  • Affected Version: 6
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2005-06-05
  • Updated: 2017-05-16
  • Resolved: 2005-09-08
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.
Other JDK 6
1.4.2_12Fixed 6 b43Fixed
Related Reports
Relates :  
Relates :  
Description
When java.lang.OutOfMemoryError is thrown because the heap or perm space is full it would be desirable to dump the java heap to a file. For example, if the VM were to dump the heap in HPROF binary format then we could browse the heap using jmap.
###@###.### 2005-06-05 19:46:31 GMT

Comments
EVALUATION -- This feature was back-ported to 5.0 update 7. It was also back-ported to 1.4.2_12 but is missing the some changes needed to work with the through-put collector (-XX:+UseParallelGC). These will included in a future update of 1.4.2.
24-07-2006

EVALUATION This was added in b43. If an application runs with -XX:+HeapDumpOnOutOfMemoryError then the heap will be dumped to a file when OutOfMemoryError is first thrown. Another option can be used to configure the name/location of the dump if required (default is java_pid<pid>.hprof in the working directory).
08-09-2005

EVALUATION This would be very useful. ###@###.### 2005-06-05 19:47:16 GMT
05-06-2005