-
-
Notifications
You must be signed in to change notification settings - Fork 925
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
jRuby 9.00.00.. crashed with JDK 1.8.u40 #2708
Comments
LOG file:
|
This appears to be a bug in the JVM, specifically in the parallel GC. I will close this and file an OpenJDK bug. Incidentally, are you able to reproduce this easily? |
Also, suggestions:
|
Hi again. I did a test with JAVA_HOME = JDK 1.8 u25 64-bit I didn't test 31 because it did bad things to the internet last time some of us used it (on all systems!), spooky. Anyhow the: jruby -S gem list --remote Command completed fine on u25. So we can say this is definitely a u40 specific issue. Our friends at Oracle added some stuff to do with .EXE packaging, you might find this is not a JVM problem as much as a JRuby build issue. Thanks for the help, w. |
@headius FYI, we had a user hit this as well: https://tickets.puppetlabs.com/browse/SERVER-858 For them, trying all sorts of other JDKs including the u25 one referenced above did not solve the problem. Switching to G1 GC does seem to have fixed it (based on early results), which seems to validate your impression that maybe it has to do with the Parallel GC... however, figured it was worth giving you a quick shout as a heads up since it seems like it may affect a broader swath of JDK versions than what this ticket implies. Will post an update or open a new issue if we learn anything new or come up with a simple repro case. |
Hi all,
--------[ console output ]--------
jruby -S gem list --remote
*** REMOTE GEMS ***
A fatal error has been detected by the Java Runtime Environment:
Failed to write core dump. Minidumps are not enabled by default on client versions of Windows
An error report file with more information is saved as:
The text was updated successfully, but these errors were encountered: