JDK-6627258 : SIGBUS in C2 compiled method - not enough swap space for thread stack (add message)
  • Type: Enhancement
  • Component: hotspot
  • Sub-Component: runtime
  • Affected Version: 6u2
  • Priority: P3
  • Status: Closed
  • Resolution: Duplicate
  • OS: solaris_10
  • CPU: x86
  • Submitted: 2007-11-07
  • Updated: 2010-12-16
  • Resolved: 2010-12-16
Related Reports
Duplicate :  
JDK-6302804 - Hotspot VM dies ungraceful death when C heap is exhausted in various places.
Description
cu test application failed 1.6.0_02 on solaris 10 amd system. stack trace: 

  [1] __lwp_kill(0x218, 0x6, 0xffffffffb844bd80, 0xfffffd7fff2f4c1e, 0x0, 0x6), at 0xfffffd7fff2f42ea
  [2] _thr_kill(0x0, 0x0, 0x0, 0x0, 0x0, 0x0), at 0xfffffd7fff2ef2d3
  [3] raise(0x0, 0x0, 0x0, 0x0, 0x0, 0x0), at 0xfffffd7fff29ce19
  [4] abort(0x0, 0x0, 0x0, 0x0, 0x0, 0x0), at 0xfffffd7fff27c970
  [5] os::abort(0x0, 0x0, 0x0, 0x0, 0x0, 0x0), at 0xfffffd7ffee7ba74
  [6] VMError::report_and_die(0x0, 0x0, 0x0, 0x0, 0x0, 0x0), at 0xfffffd7ffef87375
  [7] JVM_handle_solaris_signal(0x0, 0x0, 0x0, 0x0, 0x0, 0x0), at 0xfffffd7ffe915803
  [8] signalHandler(0x0, 0x0, 0x0, 0x0, 0x0, 0x0), at 0xfffffd7ffe915a8e
  [9] __sighndlr(0x0, 0x0, 0x0, 0x0, 0x0, 0x0), at 0xfffffd7fff2f1216
  [10] call_user_handler(0x0, 0x0, 0x0, 0x0, 0x0, 0x0), at 0xfffffd7fff2e64a2
  [11] sigacthandler(0x0, 0x0, 0x0, 0x0, 0x0, 0x0), at 0xfffffd7fff2e6688
  ---- called from signal handler with signal 10 (SIGBUS) ------
=>[12] 0xfffffd7ffb394470(0xfffffd7f7b6c1330, 0xfffffd7f7b6c1270, 0xfffffd7ff62dc138, 0xff7ffd80b803f000, 0xfffffd7f7b6a9840, 0x
15), at 0xfffffd7ffb394470
  [13] 0xfffffd7ffb3af798(0x0, 0x0, 0x0, 0x0, 0x0, 0x0), at 0xfffffd7ffb3af798
  [14] 0xfffffd7ff5fee148(0x0, 0x0, 0x0, 0x0, 0x0, 0x0), at 0xfffffd7ff5fee148
Comments
EVALUATION I have a change to catch the sig bus with ENOMEM and call vm_exit_out_of_memory() but will be fixed as part of bug 6302804. [2010-12-16T22:17:28.21] Creating threads... [2010-12-16T22:17:45.03] # There is insufficient memory for the Java Runtime Env ironment to continue. [2010-12-16T22:17:45.03] # No swap to commit thread stack [2010-12-16T22:17:45.03] # An error report file with more information is saved a s: [2010-12-16T22:17:45.03] # /net/resexhausted001/hs_err_pid1422.log [2010-12-16T22:17:45.03] [thread 2567 also had an error] [2010-12-16T22:17:45.03] [thread 2 also had an error] with hs_err_pid*.log file with: # There is insufficient memory for the Java Runtime Environment to continue. # No swap to commit thread stack # Possible solutions: # reduce memory load on the system # increase physical memory or swap space # check if swap backing store is full # decrease Java heap size (-Xmx/-Xms) # decrease number of Java threads # decrease Java thread stack sizes (-Xss) # This output file may be truncated or incomplete. # # JRE version: 7.0-b118 # Java VM: Java HotSpot(TM) Server VM (20.0-b04-6892275_1214_1557-fastdebug mixe d mode solaris-sparc ) ...
16-12-2010
EVALUATION Was this reopened, or just never closed? This might just be another one of those places where we cannot handle an OOM gracefully.
26-08-2010
EVALUATION The box is out of swap space. Closing as not a defect.
17-06-2008