JDK-6306997 : SA: jmap -permstat OOME condititon handled incorrectly
  • Type: Bug
  • Component: core-svc
  • Sub-Component: tools
  • Affected Version: 6
  • Priority: P3
  • Status: Closed
  • Resolution: Not an Issue
  • OS: generic
  • CPU: generic
  • Submitted: 2005-08-05
  • Updated: 2013-09-05
  • Resolved: 2013-09-05
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 8
8Resolved
Related Reports
Relates :  
JDK-6494472 - jmap -permstat fails with Out of swap because uses too much memory
Description
After OOME happens inside jmap it hangs completly:

Attaching to process ID 5698, please wait...
Debugger attached successfully.
Client compiler detected.
JVM version is 1.5.0-b64
finding class loader instances ..Unknown oop at 0x4592a520
Oop's klass is 0x4666bef0
Unknown oop at 0x459ec648
Oop's klass is 0x4e883334
done.
computing per loader stat ..done.
please wait.. computing liveness............................Exception in thread "Thread-1" java.lang.OutOfMemoryError: Java heap space

Moreover, after killing jmap debugee process becomes paused forever.
Comments
-permstat option has been removed
05-09-2013
EVALUATION Computing liveness of classloader objects may not of much use -- given that SA can not do accurate liveness analysis. I think this may be removed. Also, going forward -permstat may also be implemented as another attach-on-demand command (like -histo, -dump options are) for live process case.
08-06-2006