Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Critical
-
Resolution: Not A Bug
-
Affects Version/s: JRuby 1.7.0.pre1
-
Fix Version/s: None
-
Component/s: Application Error
-
Labels:None
-
Environment:Linux x86_64 (Ubuntu and Scientific Linux)
$ jruby --version
jruby 1.7.0.dev (ruby-1.8.7-p352) (2011-12-21 6b200b0) (Java HotSpot(TM) 64-Bit Server VM 1.7.0_02) [linux-amd64-java]
-
Number of attachments :
Description
This looks a lot like JRUBY-6244.
When starting our application, it ran a short while (about 20 seconds) and then crashed. This happened consistently every time. The application is a multi-threaded Eclipse RCP application. Reverting to JRuby 1.6.5 enabled us to get past the problem. Reinstating JRuby 1.7.0.dev (in test) then worked with no further crashes, probably due to changed application state. Alas, we did not keep the original state.
We wanted to use JRuby 1.7.0.dev since it has fixes for multi-threaded require/autoload, but we dare not use JRuby 1.7.0.dev in production if it crashes.
# # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x00007f5c6a595b10, pid=10168, tid=140034723018496 # # JRE version: 7.0_02-b13 # Java VM: Java HotSpot(TM) 64-Bit Server VM (22.0-b10 mixed mode linux-amd64 compressed oops) # Problematic frame: # V [libjvm.so+0x33bb10] ciMethod::resolve_invoke(ciKlass*, ciKlass*)+0xd0 # # Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again # # An error report file with more information is saved as: # /home/lars/src/Nettbuss/dispatcher.build/target_linux.gtk.x86_64/hs_err_pid10168.log # # If you would like to submit a bug report, please visit: # http://bugreport.sun.com/bugreport/crash.jsp #
Anybody got an idea what may be wrong?
