java.lang.RuntimeException: Test ERROR java.lang.RuntimeException: 'heap written to' missing from stdout/stderr

JDK Bug System | Sibabrata Sahoo | 6 months ago
tip
Your exception is missing from the Samebug knowledge base.
Here are the best solutions we found on the Internet.
Click on the to mark the helpful solution and get rewards for you help.
  1. 0

    Test: sun/tools/jhsdb/HeapDumpTest.java Platform: SunOS 5.12 (sparcv9) Log: Starting LingeredApp Command line: ['/export/home/aginfra/CommonData/jdk/bin/java' '-Xmx256m' '-cp' '/export/home/aginfra/sandbox/gresults/testoutput/svc_tools/JTwork/classes/sun/tools/jhsdb:/export/home/aginfra/sandbox/gresults/testoutput/svc_tools/JTwork/classes/lib/testlibrary:/export/home/aginfra/sandbox/gresults/testoutput/svc_tools/JTwork/classes/test/lib' 'LingeredAppWithExtendedChars' 'ea730434-7d40-426a-90a1-d779019ef1ca.lck' ] 1 Starting jmap against 12446 stdout: Attaching to process ID 12446, please wait... # # A fatal error has been detected by the Java Runtime Environment: # # SIGBUS (0xa) at pc=0xffffffff04f2ccdc, pid=12447, tid=2 # # JRE version: Java(TM) SE Runtime Environment (9.0+138) (build 9-ea+138) # Java VM: Java HotSpot(TM) 64-Bit Server VM (9-ea+138, mixed mode, tiered, compressed oops, g1 gc, solaris-sparc) # Problematic frame: # C [libproc.so.1+0x2ccdc] proc_grab_common+0x24 # # Core dump will be written. Default location: /export/home/aginfra/sandbox/gresults/testoutput/svc_tools/JTwork/scratch/core or core.12447 # # An error report file with more information is saved as: # /export/home/aginfra/sandbox/gresults/testoutput/svc_tools/JTwork/scratch/hs_err_pid12447.log # # If you would like to submit a bug report, please visit: # http://bugreport.java.com/bugreport/crash.jsp # The crash happened outside the Java Virtual Machine in native code. # See problematic frame for where to report the bug. # stderr: ----------System.err:(50/2393)---------- Sep 29, 2016 5:44:18 PM ClientCommunicatorAdmin Checker-run WARNING: Failed to check connection: java.net.ConnectException: Connection refused Sep 29, 2016 5:44:18 PM ClientCommunicatorAdmin Checker-run WARNING: stopping stdout: [Attaching to process ID 12446, please wait... # # A fatal error has been detected by the Java Runtime Environment: # # SIGBUS (0xa) at pc=0xffffffff04f2ccdc, pid=12447, tid=2 # # JRE version: Java(TM) SE Runtime Environment (9.0+138) (build 9-ea+138) # Java VM: Java HotSpot(TM) 64-Bit Server VM (9-ea+138, mixed mode, tiered, compressed oops, g1 gc, solaris-sparc) # Problematic frame: # C [libproc.so.1+0x2ccdc] proc_grab_common+0x24 # # Core dump will be written. Default location: /export/home/aginfra/sandbox/gresults/testoutput/svc_tools/JTwork/scratch/core or core.12447 # # An error report file with more information is saved as: # /export/home/aginfra/sandbox/gresults/testoutput/svc_tools/JTwork/scratch/hs_err_pid12447.log # # If you would like to submit a bug report, please visit: # http://bugreport.java.com/bugreport/crash.jsp # The crash happened outside the Java Virtual Machine in native code. # See problematic frame for where to report the bug. # ]; stderr: [] exitValue = 6 java.lang.RuntimeException: Test ERROR java.lang.RuntimeException: 'heap written to' missing from stdout/stderr at HeapDumpTest.launch(HeapDumpTest.java:84) at HeapDumpTest.launch(HeapDumpTest.java:93) at HeapDumpTest.testHeapDump(HeapDumpTest.java:103) at HeapDumpTest.main(HeapDumpTest.java:122) at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(java.base@9-ea/Native Method) at jdk.internal.reflect.NativeMethodAccessorImpl.invoke(java.base@9-ea/NativeMethodAccessorImpl.java:62) at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(java.base@9-ea/DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(java.base@9-ea/Method.java:535) at com.sun.javatest.regtest.agent.MainActionHelper$SameVMRunnable.run(MainActionHelper.java:226) at java.lang.Thread.run(java.base@9-ea/Thread.java:843) Caused by: java.lang.RuntimeException: 'heap written to' missing from stdout/stderr at jdk.testlibrary.OutputAnalyzer.shouldContain(OutputAnalyzer.java:106) at HeapDumpTest.launch(HeapDumpTest.java:80) ... 9 more JavaTest Message: Test threw exception: java.lang.RuntimeException JavaTest Message: shutting down test result: Failed. Execution failed: `main' threw exception: java.lang.RuntimeException: Test ERROR java.lang.RuntimeException: 'heap written to' missing from stdout/stderr test result: Failed. Execution failed: `main' threw exception: java.lang.RuntimeException: Test ERROR java.lang.RuntimeException: 'heap written to' missing from stdout/stderr

    JDK Bug System | 6 months ago | Sibabrata Sahoo
    java.lang.RuntimeException: Test ERROR java.lang.RuntimeException: 'heap written to' missing from stdout/stderr

    Root Cause Analysis

    1. java.lang.RuntimeException

      Test ERROR java.lang.RuntimeException: 'heap written to' missing from stdout/stderr

      at HeapDumpTest.launch()
    2. Unknown
      HeapDumpTest.main
      1. HeapDumpTest.launch(HeapDumpTest.java:84)
      2. HeapDumpTest.launch(HeapDumpTest.java:93)
      3. HeapDumpTest.testHeapDump(HeapDumpTest.java:103)
      4. HeapDumpTest.main(HeapDumpTest.java:122)
      4 frames